Repository navigation
Support supplied global-index results in batch scans - #1133
Merged
JingsongLi merged 2 commits intoOct 15, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Support the existing PyPaimon
with_global_index_resultread path in Rust core. Primary-key vector/full-text results carry physical IndexedSplits, not global row IDs. Ordinary scans currently cannot consume those captured selections, forcing the Python scanner path.Match Java
PrimaryKeyBatchScanandDataEvolutionBatchScan: preserve PK result snapshots/splits before ordinary planning, and apply DE row-ID selections and scores to the final planned ranges. Query-authorized scans ignore external raw-index selections.PyPaimon integration: apache/paimon#10591.
Brief change log
GlobalIndexResult, following Java. Retain optional source context internally for ranked reads.TableScan::with_global_index_resultandIncrementalScan::with_global_index_result; searches pass their result directly without a conversion API.totalBucketsrather than materializing it during serialization.GlobalIndexResultandGlobalIndexResultReadBuilder, with thin static transports for external ranges/scores/splits. Remove the separate tableSearchResult, PythonHybridSearchResult, and explicit conversion. Update type stubs and C/DataFusion callers.Tests
GlobalIndexResultand support ranked reads and direct scan handoff, with exact final split-score transport checks.cargo +1.98.0 clippy --locked --all-targets --workspace --features fulltext,vortex -- -D warningscargo fmt --all --checkAPI and Format
Adds the core selection APIs and unifies the public table-search result type as
GlobalIndexResult(no compatibility aliases). Existing plain-split callers keep their behavior. No table storage-format changes; the split wire reader now accepts the existing Java float-score representation.Documentation
Updated API documentation and Python type stubs.