-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-34320][SQL][FOLLOWUP] Modify V2JDBCTest to follow the change of the error message. #33074
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
cc: @HyukjinKwon @cloud-fan and @imback82 |
imback82
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HyukjinKwon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! LGTM
|
Kubernetes integration test starting |
|
Test build #140299 has finished for PR 33074 at commit
|
|
Merged to |
It's because docker-integration-tests don't depend on @HyukjinKwon We intentionally let the dependency empty after the discussion. |
|
Thank you for fixing this, @sarutak . |
|
+1, late LGTM. |
|
Kubernetes integration test status success |
|
@dongjoon-hyun Thank you! |
What changes were proposed in this pull request?
This is a followup PR for SPARK-34320 (#32854).
That PR changed the error message of
ALTER TABLEbutV2JDBCTestdidn't comply with the change.Why are the changes needed?
To fix
v2.*JDBCSuitefailure.Does this PR introduce any user-facing change?
No.
How was this patch tested?
docker-integration-tests on GA.