-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-28885][SQL][FOLLOW-UP] Re-enable the ported PgSQL regression tests of SQLQueryTestSuite #26492
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
|
Test build #113669 has finished for PR 26492 at commit
|
|
retest this please |
|
Thanks for your quick check, @MaxGekk ! cc: @dongjoon-hyun @gengliangwang |
|
Test build #113682 has finished for PR 26492 at commit
|
| 0 seconds | ||
| 3 hours 4 minutes 5 seconds | ||
| 41393 hours 19 minutes 20 seconds | ||
| 953 hours 32 minutes 1 seconds |
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.
This diff is related to the recent change: #26401
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.
Thank you for updating, @maropu .
| INSERT INTO fract_only VALUES (5, '0.99994'); | ||
| -- INSERT INTO fract_only VALUES (3, '1.0' as decimal(4,4)); -- should fail | ||
| INSERT INTO fract_only VALUES (4, cast('-0.9999' as decimal(4,4))); | ||
| INSERT INTO fract_only VALUES (5, cast('0.99994' as decimal(4,4))); |
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.
So, this is converting CASTING DURING INSERTING into CASTING WITH CAST syntax.
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.
Ur... my fault.. I'll update later.
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.
Oh, it was just a comment to clarify. I think it's okay for now AS-IS since we don't support the original query in any way.
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.
But, the original queries throw unsupported exceptions now, so most of queries in this file become invalid in Spark. In the last commit, I changed these string literals into floating-point literals for depending on INSERT assignment casts. Which do you think is better, as-is or the last commit?
| INSERT INTO TIMESTAMP_TBL VALUES ('now'); | ||
| -- PostgreSQL implicitly casts string literals to data with timestamp types, but | ||
| -- Spark does not support that kind of implicit casts. | ||
| INSERT INTO TIMESTAMP_TBL VALUES timestamp(('now')); |
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.
It seems that you wanted the following.
- INSERT INTO TIMESTAMP_TBL VALUES timestamp(('now'));
+ INSERT INTO TIMESTAMP_TBL VALUES timestamp('now');
Or,
INSERT INTO TIMESTAMP_TBL VALUES (timestamp('now'));
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.
oh, ok.
|
Test build #113751 has finished for PR 26492 at commit
|
|
@maropu Thanks for reenabling the test cases! |
| -- PostgreSQL implicitly casts string literals to data with timestamp types, but | ||
| -- Spark does not support that kind of implicit casts. | ||
| INSERT INTO TIMESTAMP_TBL VALUES timestamp(('now')); | ||
| INSERT INTO TIMESTAMP_TBL VALUES (timestamp('now')); |
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.
Did we regenerate timestamp.sql.out?
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.
Oh... I got it.
|
|
||
| -- !query 1 | ||
| INSERT INTO TIMESTAMP_TBL VALUES ('now') | ||
| INSERT INTO TIMESTAMP_TBL VALUES timestamp(('now')) |
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.
I mean this one~
|
Test build #113759 has finished for PR 26492 at commit
|
|
retest this please. |
|
Test build #113766 has finished for PR 26492 at commit
|
|
retest this please |
|
Test build #113823 has finished for PR 26492 at commit
|
|
retest this please |
|
Test build #114124 has finished for PR 26492 at commit
|
|
Ur, it seems I need to update the golden file again.. |
202988b to
7c06f0d
Compare
|
Test build #114154 has finished for PR 26492 at commit
|
dongjoon-hyun
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.
+1, LGTM. Merged to master.
|
Thanks for taking care of it, guys! @dongjoon-hyun @gengliangwang @MaxGekk |
What changes were proposed in this pull request?
SPARK-28885(#26107) has supported the ANSI store assignment rules and stopped running some ported PgSQL regression tests that violate the rules. To re-activate these tests, this pr is to modify them for passing tests with the rules.
Why are the changes needed?
To make the test coverage better.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.