-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-35509][DOCS] Move text data source options from Python and Scala into a single page #32660
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
…la into a single page.
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #138915 has finished for PR 32660 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status success |
Kubernetes integration test starting |
Kubernetes integration test status success |
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.
LGTM otherwise
Test build #138949 has finished for PR 32660 at commit
|
Test build #138952 has finished for PR 32660 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status success |
Merged to master. |
* `DataFrameWriter` | ||
* `DataStreamReader` | ||
* `DataStreamWriter` | ||
* `OPTIONS` clause at [CREATE TABLE USING DATA_SOURCE](sql-ref-syntax-ddl-create-table-datasource.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.
Sorry I missed it here. This is not in "the .option
/.options
methods of". Can you make the level down?
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.
Sure. let me fix it in #32658
Test build #138965 has finished for PR 32660 at commit
|
What changes were proposed in this pull request?
This PR proposes move text data source options from Python, Scala and Java into a single page.
Why are the changes needed?
So far, the documentation for text data source options is separated into different pages for each language API documents. However, this makes managing many options inconvenient, so it is efficient to manage all options in a single page and provide a link to that page in the API of each language.
Does this PR introduce any user-facing change?
Yes, the documents will be shown below after this change:
How was this patch tested?
Manually build docs and confirm the page.