-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-33930][SQL] Script Transform default FIELD DELIMIT should be \u0001 for no serde #30958
Conversation
FYI @maropu @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.
Not related to the change. But I notice that some contributors usually use screenshots in the description. I personally don't recommend this approach. The images cannot be indexed and searched. So I suggest that for problem and fix description, some text are more helpful.
Screenshots are usually posted for UI or doc change so we can verify the UI/doc rendering results.
Yea, thanks for your suggestion, I will update pr desc. And will pay attention to this problem. |
(1, 2, 3), | ||
(2, 3, 4), | ||
(3, 4, 5) | ||
).toDF("a", "b", "c") // Note column d's data type is Decimal(38, 18) |
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.
where is column d?
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.
where is column d?
Remove this unrelated comment. Copy code from other UT..forgot remove this comment
Spark SQL no serde row format field delimit default value is '\u0001' -> Spark SQL no serde row format field delimit default value should be '\u0001'? |
Maybe "Script Transform default FIELD DELIMIT should be \u0001 for no serde". |
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 also changes current behavior. Shall we update the SQL migration guide too?
How about current updated migration guide doc? |
docs/sql-migration-guide.md
Outdated
@@ -30,6 +30,8 @@ license: | | |||
|
|||
- In Spark 3.2, `ALTER TABLE .. RENAME TO PARTITION` throws `PartitionAlreadyExistsException` instead of `AnalysisException` for tables from Hive external when the target partition already exists. | |||
|
|||
- In Spark 3.2, script transform default `FIELD DELIMIT` is `\u0001` for no serde mode. In Spark 3.1 or earlier, the default `FIELD DELIMIT` is `\t`. |
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.
Do we need backquote? Maybe `FIELD DELIMIT`
-> FIELD DELIMIT
?
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.
Do we need backquote? Maybe
`FIELD DELIMIT`
->FIELD DELIMIT
?
Done
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.
One minor comment.
Kubernetes integration test starting |
Test build #133470 has finished for PR 30958 at commit
|
Kubernetes integration test status failure |
Kubernetes integration test starting |
Kubernetes integration test starting |
Kubernetes integration test status success |
Kubernetes integration test status failure |
Test build #133479 has finished for PR 30958 at commit
|
Test build #133484 has finished for PR 30958 at commit
|
Test build #133489 has finished for PR 30958 at commit
|
Merged to master. |
What changes were proposed in this pull request?
For same SQL
In hive:
In Spark
We should keep same. Change default ROW FORMAT FIELD DELIMIT to
\u0001
In hive default value is '1' to char is '\u0001'
Why are the changes needed?
Keep same behavior with hive
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added UT