[FLINK-39795][connect/mongodb] Fix MongoDB sharded chunk lookup to keep index-backed reads#4417
Open
yuxiqian wants to merge 2 commits into
Open
[FLINK-39795][connect/mongodb] Fix MongoDB sharded chunk lookup to keep index-backed reads#4417yuxiqian wants to merge 2 commits into
yuxiqian wants to merge 2 commits into
Conversation
…ep index-backed reads
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
1 participant
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.
This closes FLINK-39795.
The previous $or filter (ns or uuid) could prevent index-backed sorting on config.chunks, leading to in-memory sort and failures like “Sort operation used more than the maximum XXXX bytes of RAM”. Instead we choose the filter by MongoDB server version (with fallback handling) to ensure query read is in IXSCAN.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude 1.9255.2 (Claude Opus 4.7)