Page History

...

1. "Root" exception classes are HyracksDataException for runtime errors and AlgebricksException for compilation errors.
2. Exeptions declared in throws clause in method signatures must be of those types to avoid wrapping of exceptions to satisfy interfaces.
3. Every exception should contain an error code that uniquely identifies the error and the error message template. In addition to the error code each exception has a fixed set of parameters that are used to parameterize the error message. The goal of the error code is to enable error messages in different languages, evolution of error messages without breaking error identifiers, and the ability to easily search for problems (and solutions) in search engines.
4. Subclasses of the root exceptions can be used to simplify the construction of exception objects and to increase readability of the code.

Here are the key designs that we want to achieve:

--  None of the exceptions defined in AsterixDB supports a zero-parameter constructor nor a single string-parameter constructor;

--  In all constructors of the root level exception classes, there should be an error code;

--  No further exceptions should be thrown from constructing an exception defined in AsterixDB. Otherwise, the exception handling will be complicated.

Error code range:

0 --- 999: runtime errors

1000 ---- 1999: compilation errors

2000 ---- 2999: storage errors

3000 ---- 3999: feed errors

4000 ---- 4999: lifecycle management errors