-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-31181][SQL][TESTS] Remove the default value assumption on CREATE TABLE test cases #27946
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
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLParserSuite.scala
Outdated
Show resolved
Hide resolved
|
Test build #119980 has finished for PR 27946 at commit
|
|
Hi, @cloud-fan . Could you review this PR? |
|
|
||
| -- [SPARK-19842] Informational Referential Integrity Constraints Support in Spark | ||
| CREATE TABLE view_base_table (key int /* PRIMARY KEY */, data varchar(20)); | ||
| CREATE TABLE view_base_table (key int /* PRIMARY KEY */, data varchar(20)) USING PARQUET; |
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.
Shall we keep the pgsql test as what it is in pgsql?
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.
Hi, @cloud-fan . We are using CREATE TABLE USING even in pgsql test. It's okay to change this.
sql/core/src/test/scala/org/apache/spark/sql/sources/InsertSuite.scala
Outdated
Show resolved
Hide resolved
sql/hive/src/test/scala/org/apache/spark/sql/hive/StatisticsSuite.scala
Outdated
Show resolved
Hide resolved
|
Test build #120066 has finished for PR 27946 at commit
|
|
thanks, merging to master/3.0! |
|
Thank you, @cloud-fan ! Also, I closed #27894. |
…TE TABLE test cases A few `CREATE TABLE` test cases have some assumption on the default value of `LEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED`. This PR (SPARK-31181) makes the test cases more explicit from test-case side. The configuration change was tested via #27894 during discussing SPARK-31136. This PR has only the test case part from that PR. This makes our test case more robust in terms of the default value of `LEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED`. Even in the case where we switch the conf value, that will be one-liner with no test case changes. No. Pass the Jenkins with the existing tests. Closes #27946 from dongjoon-hyun/SPARK-EXPLICIT-TEST. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Wenchen Fan <[email protected]> (cherry picked from commit f1cc867) Signed-off-by: Dongjoon Hyun <[email protected]>
…TE TABLE test cases ### What changes were proposed in this pull request? A few `CREATE TABLE` test cases have some assumption on the default value of `LEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED`. This PR (SPARK-31181) makes the test cases more explicit from test-case side. The configuration change was tested via apache#27894 during discussing SPARK-31136. This PR has only the test case part from that PR. ### Why are the changes needed? This makes our test case more robust in terms of the default value of `LEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED`. Even in the case where we switch the conf value, that will be one-liner with no test case changes. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Pass the Jenkins with the existing tests. Closes apache#27946 from dongjoon-hyun/SPARK-EXPLICIT-TEST. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Wenchen Fan <[email protected]>
What changes were proposed in this pull request?
A few
CREATE TABLEtest cases have some assumption on the default value ofLEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED. This PR (SPARK-31181) makes the test cases more explicit from test-case side.The configuration change was tested via #27894 during discussing SPARK-31136. This PR has only the test case part from that PR.
Why are the changes needed?
This makes our test case more robust in terms of the default value of
LEGACY_CREATE_HIVE_TABLE_BY_DEFAULT_ENABLED. Even in the case where we switch the conf value, that will be one-liner with no test case changes.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the Jenkins with the existing tests.