[SPARK-41154][SQL][3.3] Incorrect relation caching for queries with time travel spec #38741
Conversation
This file contains 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
cloud-fan
approved these changes
Nov 21, 2022
huaxingao
approved these changes
Nov 21, 2022
|
tests all passed: https://github.com/ulysses-you/spark/runs/9613393804 |
|
thanks, merging to 3.3! |
cloud-fan
pushed a commit
that referenced
this pull request
Nov 22, 2022
…ime travel spec backport #38687 for branch-3.3 ### What changes were proposed in this pull request? Add TimeTravelSpec to the key of relation cache in AnalysisContext. ### Why are the changes needed? Correct the relation resolution for the same table but different TimeTravelSpec. ### Does this PR introduce _any_ user-facing change? yes, bug fix ### How was this patch tested? add test Closes #38741 from ulysses-you/time-travel-spec-3.3. Authored-by: ulysses-you <ulyssesyou18@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
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.
backport #38687 for branch-3.3
What changes were proposed in this pull request?
Add TimeTravelSpec to the key of relation cache in AnalysisContext.
Why are the changes needed?
Correct the relation resolution for the same table but different TimeTravelSpec.
Does this PR introduce any user-facing change?
yes, bug fix
How was this patch tested?
add test