We were running SingleStore 7.9.5 in a self-managed cluster before, and everything was working well till we decided to spin up a new cluster with the latest 8.1.x
The pipelines which were running well in the previous clusters, threw an error.
There were two kinds for a single pipeline:
**ERROR_KIND** **ERROR_CODE** **ERROR_MESSAGE**
Internal 1264 Out of range value for column 'is_holiday'
Internal 2312 Out of range value
The above output was from the below SQL query to check pipeline errors
SELECT DATABASE_NAME, PIPELINE_NAME, BATCH_ID, PARTITION, BATCH_SOURCE_PARTITION_ID,
ERROR_KIND, ERROR_CODE, ERROR_MESSAGE, LOAD_DATA_LINE_NUMBER, LOAD_DATA_LINE
FROM information_schema.PIPELINES_ERRORS
WHERE DATABASE_NAME = 'mydb';
Could it be on the older version you had the data_conversion_compatibility_level set to a different level than on the new 8.1 version?
The error: “Out of range value for column” in SingleStore typically occurs when an attempt is made to insert a value that is larger than the maximum limit or smaller than the minimum limit of a column’s datatype
In SingleStore version 8.1, the handling of data conversions was extended to include stricter checking of the data conversion by using the global sync variable data_conversion_compatibility_level. This variable controls the way certain data conversions are performed.
If this variable is set to ‘6.0’, you should be able to insert a value that is out of range without any error message, but the actual value will be up or down to the range limit value.