-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Docs: Update SQL status page #6736
Conversation
dbba77a
to
0048678
Compare
|
||
## Runtime | ||
|
||
- [x] Streaming Grouping |
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.
I am not sure if there are other features to highlight in the RUNTIME
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.
Thank you! @alamb
- [x] `SHOW CREATE TABLE <view>` | ||
- [x] Basic SQL [Information Schema](./information_schema.md) (`TABLES`, `VIEWS`, `COLUMNS`) | ||
- [ ] Full SQL [Information Schema](./information_schema.md) support | ||
- [x] Support for nested types (`ARRAY`/`LIST` and `STRUCT`)- see [Array Functions](./scalar_functions.md#array-functions) |
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.
I'm not sure whether DF have fully supported it
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.
Yes, you are right that the support is only partial - I'll see if I can find some way to make this clearer
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.
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.
I think good JSON support is very important for Datafusion to get more traction in the general community. SQL2023 has some good stuff about this (see here for a good summary.).
While we are on the SQL support/ease-of-use topic, this DuckDB page is also a good list of desiderata for us (some of these we implemented already).
I plan to actively talk about/promote Datafusion in various venues once we get into a state where these things "just work".
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.
I think good JSON support is very important for Datafusion to get more traction in the general community. SQL2023 has some good stuff about this (see here for a good summary.).
I agree.
While we are on the SQL support/ease-of-use topic, this DuckDB page is also a good list of desiderata for us (some of these we implemented already).
It would be great to file tickets about these features -- I have found clearly written tickets with a "good first issue" often attracts contributions. If you have a chance to file the tickets that would be awesome, otherwise I will try and find time to do so
I plan to actively talk about/promote Datafusion in various venues once we get into a state where these things "just work".
I think it is a balance -- part of the way we grow the DataFusion community (to get the resources to make it better) is to talk about it publically.
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 will file tickets for these 👍
- [x] Write support | ||
- [x] Field access (`col['field']` and [`col[1]`]) | ||
- [x] [Array Functions](./scalar_functions.md#array-functions) | ||
- [ ] [Struct Functions](./scalar_functions.md#struct-functions) |
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 link will work after #6754 is merged
- [x] Schemas (`CREATE / DROP SCHEMA`) | ||
- [x] Tables (`CREATE / DROP TABLE`, `CREATE TABLE AS SELECT`) | ||
- [ ] Data Insert | ||
- [x] `INSERT INTO` |
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 @alamb that is not very clear to me.
Do you mean DF supports SQL syntax to insert data into CSV file?
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.
Yes, that is correct Here is an example:
(arrow_dev) alamb@MacBook-Pro-8:~/Software/arrow-site$ touch /tmp/foo.csv
(arrow_dev) alamb@MacBook-Pro-8:~/Software/arrow-site$ datafusion-cli
DataFusion CLI v26.0.0
❯ create external table foo (x int) stored as csv location '/tmp/foo.csv';
0 rows in set. Query took 0.004 seconds.
❯ insert into foo values (1), (2), (3);
+-------+
| count |
+-------+
| 3 |
+-------+
1 row in set. Query took 0.005 seconds.
❯
\q
(arrow_dev) alamb@MacBook-Pro-8:~/Software/arrow-site$ cat /tmp/foo.csv
1
2
3
The UX is somewhat awkward at the moment as it can only append into existing files (not create new ones). I have real hopes it will be improved
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.
Oh that is really cool, I want to make this happen for parquet asap. Will create a ticket and implement it. Should be straightfwd as we have parquetwriter
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.
Which issue does this PR close?
re #3058
Rationale for this change
Someone internally at InfluxData was referring to the SQL status page in DataFusion and since it was out of date it was confusing
While updating this page it turns out DataFusion has quite a lot of features now
What changes are included in this PR?
Update the SQL status page -- I also removed several lists of functions that had their own documentation page rather than trying to keep two lists up to date
Here is an example of the new page rendered:
Are these changes tested?
N/A
Are there any user-facing changes?
Better docs