-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-53694][SQL][TESTS] Improve V1WriteHiveCommandSuite test coverage
#52436
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 @cloud-fan |
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.
According to the claims, why don't we use spark.sql.legacy.createHiveTableByDefault=(true|false) explicitly to improve the test coverage, @pan3793 ?
Previously, V1WriteHiveCommandSuite uses CREATE TABLE without declaring USING or STORED AS, which relies on spark.sql.legacy.createHiveTableByDefault's default value, SPARK-46122 changes the default value of spark.sql.legacy.createHiveTableByDefault from true to false, which implicitly affects this test suite.
|
@dongjoon-hyun the test suite hierarchy is
|
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. Got it., @pan3793 .
V1WriteHiveCommandSuite test coverage
|
Merged to master for Apache Spark 4.1.0-preview3. |
…rage ### What changes were proposed in this pull request? Previously, `V1WriteHiveCommandSuite` uses `CREATE TABLE` without declaring `USING` or `STORED AS`, which relies on `spark.sql.legacy.createHiveTableByDefault`'s default value, SPARK-46122 changes the default value of `spark.sql.legacy.createHiveTableByDefault` from `true` to `false`, which implicitly affects this test suite. In addition, we should take `spark.sql.hive.convertMetastoreParquet` and `spark.sql.hive.convertMetastoreOrc` into account in `V1WriteHiveCommandSuite` ### Why are the changes needed? Restore and improve test coverage. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GHA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#52436 from pan3793/SPARK-53694. Authored-by: Cheng Pan <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
… coverage Backport #52436 to branch-4.0 to recover CI. ### What changes were proposed in this pull request? Previously, `V1WriteHiveCommandSuite` uses `CREATE TABLE` without declaring `USING` or `STORED AS`, which relies on `spark.sql.legacy.createHiveTableByDefault`'s default value, SPARK-46122 changes the default value of `spark.sql.legacy.createHiveTableByDefault` from `true` to `false`, which implicitly affects this test suite. In addition, we should take `spark.sql.hive.convertMetastoreParquet` and `spark.sql.hive.convertMetastoreOrc` into account in `V1WriteHiveCommandSuite` ### Why are the changes needed? Restore and improve test coverage. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GHA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #52683 from pan3793/SPARK-53694-4.0. Authored-by: Cheng Pan <[email protected]> Signed-off-by: Peter Toth <[email protected]>
… coverage Backport apache#52436 to branch-4.0 to recover CI. ### What changes were proposed in this pull request? Previously, `V1WriteHiveCommandSuite` uses `CREATE TABLE` without declaring `USING` or `STORED AS`, which relies on `spark.sql.legacy.createHiveTableByDefault`'s default value, SPARK-46122 changes the default value of `spark.sql.legacy.createHiveTableByDefault` from `true` to `false`, which implicitly affects this test suite. In addition, we should take `spark.sql.hive.convertMetastoreParquet` and `spark.sql.hive.convertMetastoreOrc` into account in `V1WriteHiveCommandSuite` ### Why are the changes needed? Restore and improve test coverage. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GHA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#52683 from pan3793/SPARK-53694-4.0. Authored-by: Cheng Pan <[email protected]> Signed-off-by: Peter Toth <[email protected]>
…rage ### What changes were proposed in this pull request? Previously, `V1WriteHiveCommandSuite` uses `CREATE TABLE` without declaring `USING` or `STORED AS`, which relies on `spark.sql.legacy.createHiveTableByDefault`'s default value, SPARK-46122 changes the default value of `spark.sql.legacy.createHiveTableByDefault` from `true` to `false`, which implicitly affects this test suite. In addition, we should take `spark.sql.hive.convertMetastoreParquet` and `spark.sql.hive.convertMetastoreOrc` into account in `V1WriteHiveCommandSuite` ### Why are the changes needed? Restore and improve test coverage. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GHA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#52436 from pan3793/SPARK-53694. Authored-by: Cheng Pan <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
Previously,
V1WriteHiveCommandSuiteusesCREATE TABLEwithout declaringUSINGorSTORED AS, which relies onspark.sql.legacy.createHiveTableByDefault's default value, SPARK-46122 changes the default value ofspark.sql.legacy.createHiveTableByDefaultfromtruetofalse, which implicitly affects this test suite.In addition, we should take
spark.sql.hive.convertMetastoreParquetandspark.sql.hive.convertMetastoreOrcinto account inV1WriteHiveCommandSuiteWhy are the changes needed?
Restore and improve test coverage.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GHA.
Was this patch authored or co-authored using generative AI tooling?
No.