Skip to content

Minor: document syntax of CREATE EXTERNAL TABLE #6247

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

Merged
merged 2 commits into from
May 8, 2023

Conversation

alamb
Copy link
Contributor

@alamb alamb commented May 5, 2023

Which issue does this PR close?

Rationale for this change

When writing tests yesterday it was quite challenging to remember the exact CREATE EXTERNAL table syntax so I want to document it for next time

What changes are included in this PR?

add doc comments and update DDL user guide

Are these changes tested?

N/A

Are there any user-facing changes?

Docs

@alamb alamb added the documentation Improvements or additions to documentation label May 5, 2023
@alamb alamb marked this pull request as ready for review May 5, 2023 10:47
@github-actions github-actions bot added sql SQL Planner and removed documentation Improvements or additions to documentation labels May 5, 2023

<ordered_column_list> := (<column_name> <sort_clause>, ...)

<key_value_list> := (<literal> <literal, <literal> <literal>, ...)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a collection of available options? If someone were to implement a mechanism based on options, how should it be documented?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think any option is (yet) handled by datafusion core

I believe datafusion-cli handles some: https://arrow.apache.org/datafusion/user-guide/cli.html#registering-s3-data-sources

@r4ntix maybe knows more

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone were to implement a mechanism based on options, how should it be documented?

I recommend anything meant to be used by users of datafusion should be explicitly in the CREATE TABLE syntax -- e.g. #6248)

If we do want to do something with options, perhaps it could be documented in https://arrow.apache.org/datafusion/user-guide/sql/ddl.html

Copy link
Contributor

@r4ntix r4ntix May 5, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think any option is (yet) handled by datafusion core

I believe datafusion-cli handles some: https://arrow.apache.org/datafusion/user-guide/cli.html#registering-s3-data-sources

@r4ntix maybe knows more

@alamb Yes, not all options are supported in datafusion-core. There is no actual [ OPTIONS (<key_value_list>) ] support in the current datafusion-core.

@metesynnada Do you mean that for all the [ ... ] options, do we need to be more detailed in the documentation? 🤔️

@alamb alamb added the documentation Improvements or additions to documentation label May 5, 2023
@github-actions github-actions bot removed the documentation Improvements or additions to documentation label May 5, 2023
@alamb alamb merged commit c6fa265 into apache:main May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sql SQL Planner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants