lxy-9602 opened a new pull request, #481: URL: https://github.com/apache/paimon-cpp/pull/481
<!-- PR titles must follow Conventional Commits: <type>(<optional-scope>): <description> --> ### Purpose <!-- Linking this pull request to the issue --> Linked issue: close #480 Blob fallback currently materializes every sequence layer before selecting the newest non-placeholder value. This adds unnecessary payload reads and collection decoding when newer layers already provide the result. Resolve rows from newest to oldest and skip older payloads once a value, including an explicit null, has been selected. A per-file BlobReadContext bounds each read/skip run while preserving the existing field mapping, row tracking, bitmap selection, and deletion-vector processing. Consume bounded batches directly, removing pending-batch buffering and redundant chunk offsets. <!-- What is the purpose of the change --> ### Tests Added coverage for: - Multi-layer fallback, explicit nulls, gaps, different batch sizes, and EOF alignment. - Bounded reads and payload skipping with bitmap selection, deletion vectors, and row tracking. - Covered ARRAY/MAP payloads being skipped. - Oversized batches being rejected and temporary read requests being restored. <!-- List UT and IT cases to verify this change --> ### API and Format <!-- Does this change affect API in include dir or storage format or protocol --> ### Documentation <!-- Does this change introduce a new feature --> ### Generative AI tooling Generated-by: OpenAI Codex (GPT-6) <!-- If generative AI tooling has been used in the process of authoring this patch, please include the phrase: 'Generated-by: ' followed by the name of the tool and its version. If no, write 'No'. Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details. --> -- 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]
