XuQianJin-Stars opened a new pull request, #1370: URL: https://github.com/apache/fluss/pull/1370
This PR implements the foundation layer for complex data types support: https://github.com/apache/fluss/issues/816 Core Abstractions: - DataGetters: Abstract interface for data access operations - DataSetters: Abstract interface for data setting operations - Enhanced InternalRow interface with DataGetters support Memory Management: - AbstractPagedInputView: Abstract base for paged input views - ManagedPagedOutputView: Managed paged output view implementation - MemorySegmentInputView: Memory segment input view - MemorySegmentOutputView: Memory segment output view - Enhanced InputView/OutputView interfaces Serialization Framework: - Serializer: Core serialization interface - DataInputDeserializer: Data input deserialization - DataOutputSerializer: Data output serialization - PagedTypeSerializer: Paged type serialization - SerializerSingleton: Serializer singleton management Base Serializers: - BooleanSerializer, ByteSerializer, ShortSerializer - IntSerializer, LongSerializer, FloatSerializer, DoubleSerializer - BinarySerializer, BinaryStringSerializer - DecimalSerializer, TimestampLtzSerializer, TimestampNtzSerializer - NullableSerializer: Nullable value handling Utility Classes: - VarLengthIntUtils: Variable length integer encoding/decoding - InstantiationUtil: Object instantiation utilities - InternalRowUtils: Internal row utilities - ArrayUtils: Array manipulation utilities - Pair: Generic pair implementation - MurmurHashUtils: Murmur hash implementation Type System Extensions: - DataTypeChecks: Data type validation utilities - DataTypeDefaultVisitor: Default visitor implementation - DataTypeVisitor: Visitor pattern for data types - VarBinaryType, VarCharType, MultisetType: New type definitions Test Coverage: - Comprehensive test suite for all serializers - SerializerTestBase: Base test framework - SerializerTestInstance: Test instance management - Individual test classes for each serializer This foundation provides the necessary abstractions and infrastructure for supporting Array, Map, and Row data types in subsequent PRs. <!-- *Thank you very much for contributing to Fluss - we are happy that you want to help us improve Fluss. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.* ## Contribution Checklist - Make sure that the pull request corresponds to a [GitHub issue](https://github.com/alibaba/fluss/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no issue. - Name the pull request in the format "[component] Title of the pull request", where *[component]* should be replaced by the name of the component being changed. Typically, this corresponds to the component label assigned to the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are unsure about which is the best component. - Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review. - Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. - Each pull request should address only one issue, not mix up code from multiple issues. **(The sections below can be removed for hotfixes or typos)** --> ### Purpose <!-- Linking this pull request to the issue --> Linked issue: close https://github.com/apache/fluss/issues/1369 <!-- What is the purpose of the change --> ### Brief change log <!-- Please describe the changes made in this pull request and explain how they address the issue --> ### Tests <!-- List UT and IT cases to verify this change --> ### API and Format <!-- Does this change affect API or storage format --> ### Documentation <!-- Does this change introduce a new feature --> -- 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]
