[HUDI-4770][Stacked on 4294] Adapt spark query engine to use secondary index when querying data #6712
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
huberylee
force-pushed
the
HUDI-4770-ConvertSparkFilterToIndexFitler
branch
2 times, most recently
from
c811d09 to
4d34a8a
Compare
huberylee
force-pushed
the
HUDI-4770-ConvertSparkFilterToIndexFitler
branch
from
4d34a8a to
8d40470
Compare
Collaborator
yihua
added
priority:blocker
Contributor
|
hey @huberylee : Is there an RFC around this. |
Contributor
Author
Yes, this PR is part of the secondary index implementation. RFC is in another PR: #5370 |
Contributor
|
Hi @huberylee , are you still actively working on this PR and resolving conflicts? |
Closed
5 tasks
nsivabalan
added
priority:critical
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Change Logs
Convert spark filter to index filter, acquire and push down hit row id set.
Impact
Tables which have secondary indices will use secondary index to query hit row id set when using spark query engine.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist