ilicmarkodb opened a new pull request, #54340:
URL: https://github.com/apache/spark/pull/54340
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
Fixed `SHOW CREATE TABLE` for tables / views to correctly print `DEFAULT
COLLATION collationName`.
For example: `CREATE TABLE t (c1 STRING) DEFAULT COLLATION UTF8_LCASE`.
Previously, it was printing `COLLATE 'UTF8_LCASE'`, which produces a parsing
error.
For `UTF8_BINARY` collated / non collated columns (for example, `c1`), the
output of `SHOW CREATE TABLE` should print `c1 STRING COLLATE UTF8_BINARY`, so
that we don’t inherit the collation from the table or schema, if defined.
To achieve this, I changed `typeName` in `StringType` to print `COLLATE
UTF8_BINARY` for explicitly collated `UTF8_BINARY` columns. For non-collated
`StringType` (case object), `typeName` does not print `COLLATE UTF8_BINARY`,
which matches the old behaviour.
### Why are the changes needed?
Bug fix.
### Does this PR introduce _any_ user-facing change?
Yes, corrects `SHOW CREATE TABLE` command.
### How was this patch tested?
`show-create-table.sql` golden file.
### Was this patch authored or co-authored using generative AI tooling?
No.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
