LuciferYang opened a new issue, #9772:
URL: https://github.com/apache/paimon/issues/9772
### Bug description
`ARRAY<VECTOR(n)>` is accepted by schema validation and readable via
`ColumnarArray.getVector`, but the binary data path rejects it:
- `InternalArray.createElementGetter` has no `VECTOR` case, and
`InternalArraySerializer` builds its element getter eagerly in the constructor,
so building a serializer over such a row type throws
`IllegalArgumentException("type VECTOR not support in ...")`.
- `BinaryArray.calculateFixLengthPartSize` and `BinaryRow`-style
`getDataClass` (`InternalRow.getDataClass`) also lack VECTOR, so even past
construction, serializing/copying such an array throws `Unsupported type:
VECTOR<...>`.
- `BinaryArray.getVector` is an unconditional throw.
Concrete failing flow: a primary-key table with an `ARRAY<VECTOR(3)>` column
— the local merge (`SortBufferLocalMerger` →
`InternalRowSerializer.toBinaryRow`) serializes the row and crashes.
### Expected behavior
Nested VECTOR should flow through the same binary accessors as ARRAY/MAP/ROW
(the row-level `getVector` and
`BinaryWriter.writeVector`/`InternalVectorSerializer` already support it).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
