Status Codes

A sample solution as IoTDB requires registering the time series first before writing data is:

1. try {
2. writeData();
3. } catch (SQLException e) {
4. // the most case is that the time series does not exist
5. if (e.getMessage().contains("exist")) {
6. //However, using the content of the error message is not so efficient
7. registerTimeSeries();
8. //write data once again
9. writeData();
10. }
11. }

With Status Code, instead of writing codes like if (e.getErrorMessage().contains("exist")), we can simply use e.getErrorCode() == TSStatusCode.TIME_SERIES_NOT_EXIST_ERROR.getStatusCode().

Here is a list of Status Code and related message:

All exceptions are refactored in the latest version by extracting uniform message into exception classes. Different error codes are added to all exceptions. When an exception is caught and a higher-level exception is thrown, the error code will keep and pass so that users will know the detailed error reason. A base exception class “ProcessException” is also added to be extended by all exceptions.