[SPARK-37540][SQL] Detect more unsupported time travel#34802
Closed
cloud-fan wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-37540][SQL] Detect more unsupported time travel#34802cloud-fan wants to merge 1 commit intoapache:masterfrom
cloud-fan wants to merge 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
cc @huaxingao |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
huaxingao
approved these changes
Dec 3, 2021
|
Test build #145910 has finished for PR 34802 at commit
|
Contributor
Author
|
thanks for the review, merging to master! |
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
3 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.
What changes were proposed in this pull request?
This PR detects unsupported time travel in more places:
parquet.`/path` VERSION AS OF ...)WITH t ... FROM t VERSION AS OF)Why are the changes needed?
better error message
Does this PR introduce any user-facing change?
This feature is not released yet.
How was this patch tested?
new tests