XuQianJin-Stars opened a new pull request, #2308: URL: https://github.com/apache/fluss/pull/2308
### Purpose Linked issue: close #2257 This PR adds support for MAP data types when tiering data from Fluss to Apache Paimon. Previously, MAP types were not properly handled during the tiering process, which limited the ability to tier tables containing MAP columns to Paimon. ### Brief change log - Added `FlussMapAsPaimonMap` adapter class to convert Fluss InternalMap to Paimon InternalMap format - Added `PaimonMapAsFlussMap` adapter class to wrap Paimon InternalMap as Fluss InternalMap for reading - Enhanced `FlussRowAsPaimonRow` to support `getMap()` method for handling MAP type fields by wrapping Fluss maps with proper key and value type information - Enhanced `FlussArrayAsPaimonArray` to support nested MAP types within arrays - Enhanced `PaimonRowAsFlussRow` and `PaimonArrayAsFlussArray` to support bidirectional MAP type conversion - Updated documentation to include MAP\<kt, vt\> type mapping in the Paimon data type mapping table ### Tests - `FlussRecordAsPaimonRowTest.testMapTypeWithIntegerKeyValue`: Verifies basic MAP type with integer keys and values - `FlussRecordAsPaimonRowTest.testMapTypeWithStringKeyIntValue`: Verifies MAP type with string keys and integer values - `FlussRecordAsPaimonRowTest.testNestedMapType`: Verifies nested MAP types (MAP containing MAP as values) - `FlussRecordAsPaimonRowTest.testMapWithComplexTypes`: Verifies MAP type with complex value types like DECIMAL - `FlussRowAsPaimonRowTest`: Contains additional test cases for MAP type handling in row conversion ### API and Format This change does not affect API or storage format. It enables an existing data type (MAP) to be properly handled during the tiering process to Paimon. ### Documentation Yes, this change extends support for an existing feature. The documentation has been updated to include MAP\<kt, vt\> in the Paimon data type mapping table. -- 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]
