-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35159][SQL][DOCS] Extract hive format doc #32264
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
|
I am not sure if we need to put this page in which menu page |
|
Test build #137710 has finished for PR 32264 at commit
|
|
Test build #137711 has finished for PR 32264 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
docs/sql-ref-syntax-hive-format.md
Outdated
|
|
||
| ### Description | ||
|
|
||
| Spark support Hive format in `CREATE TABLE` clause and `TRANSFORM` clause, Hive format support |
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.
Spark supports Hive format in `CREATE TABLE` clause and `TRANSFORM` clause,
to specify serde or text delimeter.
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.
Done
docs/sql-ref-syntax-hive-format.md
Outdated
|
|
||
| * **row_format** | ||
|
|
||
| Use the `SERDE` clause to specify a custom SerDe for one table or processing inputs and outputs data. Otherwise, use the `DELIMITED` clause to use the native SerDe and specify the delimiter, escape character, null character and so on. |
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 put it in Description at the beginning?
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.
Done
docs/sql-ref-syntax-hive-format.md
Outdated
|
|
||
| Use the `SERDE` clause to specify a custom SerDe for one table or processing inputs and outputs data. Otherwise, use the `DELIMITED` clause to use the native SerDe and specify the delimiter, escape character, null character and so on. | ||
|
|
||
| * **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.
we can merge this with the next one. SERDE serde_class
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.
Done
We don't need to put it in the menu page. |
|
Test build #137732 has finished for PR 32264 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
docs/sql-ref-syntax-hive-format.md
Outdated
| --- | ||
| layout: global | ||
| title: Data Retrieval | ||
| displayTitle: Data Retrieval |
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.
In this case, shall we add a reference to this sql-ref-syntax-hive-format.md into sql-ref-syntax-qry.md?
Oh, got it. I saw @cloud-fan 's comment, We don't need to put it in the menu page. Nvm.
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, refer this in other menu doc is so strange and it's refer in two syntax doc with different type.
docs/sql-ref-syntax-hive-format.md
Outdated
| Spark supports Hive format in `CREATE TABLE` clause and `TRANSFORM` clause, | ||
| to specify serde or text delimeter. In `row_format`, uses the `SERDE` clause to specify a custom SerDe | ||
| for one table or processing inputs and outputs data. Otherwise, use the `DELIMITED` clause | ||
| to use the native SerDe and specify the delimiter, escape character, null character and so on. |
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.
how about this
There are two ways to specify the `row_format`:
1. Use the `SERDE` clause to specify a custom SerDe class
2. Use the `DELIMITED` clause to specify the delimiter ... and so on for the native text 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.
Year, more clear
|
@maropu do you want to take a look? |
|
Test build #137797 has finished for PR 32264 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
| * **row_format** | ||
|
|
||
| Used for escape mechanism. | ||
| All descriptions about syntax in `row_format` can refer to [HIVE FORMAT](sql-ref-syntax-hive-format.html) |
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.
How about Specifies the row format for input and output. See [HIVE ROW FORMAT](...) for more syntax details.?
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.
Done
|
Could you add the screenshot of the new page in the PR description? |
|
NOTE: I'm planning to backport this PR and #31010 into branch-3.1/3.0 because I think these document pages are useful for users. |
DOne |
|
Test build #137837 has finished for PR 32264 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
thanks, merging to master! |
|
thanks, merging to master! |
|
@maropu shall we have a single backport PR or two? |
|
They have different jira tickets, so I think its better to backport them separately. Could you? @AngersZhuuuu |
|
Anyway, late lgtm. Thank you, @AngersZhuuuu |
ping |
Hmmm, have conflict? need me to create backport PR? |
|
yea, yes. I couldn't cherry-pick them into the previous branches. |
Ok, ping you later when PR is ready |
### What changes were proposed in this pull request? Extract common doc about hive format for `sql-ref-syntax-ddl-create-table-hiveformat.md` and `sql-ref-syntax-qry-select-transform.md` to refer.  ### Why are the changes needed? Improve doc ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Not need Closes apache#32264 from AngersZhuuuu/SPARK-35159. Authored-by: Angerszhuuuu <angers.zhu@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
### What changes were proposed in this pull request? Extract common doc about hive format for `sql-ref-syntax-ddl-create-table-hiveformat.md` and `sql-ref-syntax-qry-select-transform.md` to refer.  ### Why are the changes needed? Improve doc ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Not need Closes apache#32264 from AngersZhuuuu/SPARK-35159. Authored-by: Angerszhuuuu <angers.zhu@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
What changes were proposed in this pull request?
Extract common doc about hive format for
sql-ref-syntax-ddl-create-table-hiveformat.mdandsql-ref-syntax-qry-select-transform.mdto refer.Why are the changes needed?
Improve doc
Does this PR introduce any user-facing change?
No
How was this patch tested?
Not need