Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Before carbon 2.0, complex child length is stored as SHORT for string, varchar, binary, date, decimal types.
So, In 2.0 as it is stored as INT, presto complex query code always assumes it as INT
and goes to out of bound exception when old store is queried.
If INT_LENGTH_COMPLEX_CHILD_BYTE_ARRAY encoding is present, parse as INT, else parse as SHORT.
so, that both stores can be queried.