[SPARK-38566][SQL][3.3] Revert the parser changes for DEFAULT column support - #35875
Closed
MaxGekk wants to merge 5 commits into
Closed
[SPARK-38566][SQL][3.3] Revert the parser changes for DEFAULT column support#35875MaxGekk wants to merge 5 commits into
MaxGekk wants to merge 5 commits into
Conversation
…n values" This reverts commit e21cb62.
Member
Author
|
It seems tests wasn't triggered. Let's wait for #35876 |
Member
|
Just merged. You might have to sync and rebase ... |
Member
Author
|
@HyukjinKwon I have rebased on recent changes but GAs are not triggered here. Do you have any ideas why this could happen? |
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
2 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?
Revert the commit e21cb62 from
branch-3.3.Why are the changes needed?
See discussion in the PR #35690.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By existing test suites.