-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-19587][SQL] bucket sorting columns should not be picked from partition columns #16931
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -169,19 +169,20 @@ class BucketedWriteSuite extends QueryTest with SQLTestUtils with TestHiveSingle | |
| } | ||
| } | ||
|
|
||
| test("write bucketed data with the overlapping bucketBy and partitionBy columns") { | ||
| intercept[AnalysisException](df.write | ||
| test("write bucketed data with the overlapping bucketBy/sortBy and partitionBy columns") { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not related to this PR, but I think we should move most test cases to sql packages. Let me try to do it. Only orc formats are hive only. |
||
| val e1 = intercept[AnalysisException](df.write | ||
| .partitionBy("i", "j") | ||
| .bucketBy(8, "j", "k") | ||
| .sortBy("k") | ||
| .saveAsTable("bucketed_table")) | ||
| } | ||
| assert(e1.message.contains("bucketing column 'j' should not be part of partition columns")) | ||
|
|
||
| test("write bucketed data with the identical bucketBy and partitionBy columns") { | ||
| intercept[AnalysisException](df.write | ||
| .partitionBy("i") | ||
| .bucketBy(8, "i") | ||
| val e2 = intercept[AnalysisException](df.write | ||
| .partitionBy("i", "j") | ||
| .bucketBy(8, "k") | ||
| .sortBy("i") | ||
| .saveAsTable("bucketed_table")) | ||
| assert(e2.message.contains("bucket sorting column 'i' should not be part of partition columns")) | ||
| } | ||
|
|
||
| test("write bucketed data without partitionBy") { | ||
|
|
||
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.
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.
Orthogonal to your PR: This means Spark supports buckets in range [1, 99999]. Any reason to have a low value for upper bound ?
Also, I don't think this code gets executed if the bucketed table is written via SQL. The only check I can see was when we create
BucketSpecbut its for lower bound only :spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
Line 138 in 4d4d0de
BucketSpeccreation to be consistent across the codebase.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.
yea we should move this check to
BucketSpecfor consistency.About the upper bound, we just picked a value that should be big enough. In practice I don't think users will set large bucket numbers, this is just a sanity check.
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.
Cool. I will submit a PR for that change once you land this one
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.
or you could do that change right here
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.
feel free to submit one :)