Docs: Update SQL status page #6736
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -34,106 +34,63 @@ | |
|
|
||
| ## SQL Support | ||
|
|
||
| - [x] Projection (`SELECT`) | ||
| - [x] Filter (`WHERE`) | ||
| - [x] Filter post-aggregate (`HAVING`) | ||
| - [x] Sorting (`ORDER BY`) | ||
| - [x] Limit (`LIMIT` | ||
| - [x] Aggregate (`GROUP BY`) | ||
| - [x] cast /try_cast | ||
| - [x] [`VALUES` lists](https://www.postgresql.org/docs/current/queries-values.html) | ||
| - [x] [String Functions](./scalar_functions.md#string-functions) | ||
| - [x] [Conditional Functions](./scalar_functions.md#conditional-functions) | ||
| - [x] [Time and Date Functions](./scalar_functions.md#time-and-date-functions) | ||
| - [x] [Math Functions](./scalar_functions.md#math-functions) | ||
| - [x] [Aggregate Functions](./aggregate_functions.md) (`SUM`, `MEDIAN`, and many more) | ||
| - [x] Schema Queries | ||
| - [x] `SHOW TABLES` | ||
| - [x] `SHOW COLUMNS FROM <table/view>` | ||
| - [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) | ||
| - [x] Nested types (`ARRAY`/`LIST` and `STRUCT`)- see [Array Functions](./scalar_functions.md#array-functions) | ||
| - [x] Subqueries | ||
| - [x] Common Table Expressions (CTE) | ||
| - [x] Set Operations (`UNION [ALL]`, `INTERSECT [ALL]`, `EXCEPT[ALL]`) | ||
| - [x] Joins (`INNER`, `LEFT`, `RIGHT`, `FULL`, `CROSS`) | ||
| - [x] Window Functions | ||
| - [x] Empty (`OVER()`) | ||
| - [x] Partitioning and ordering: (`OVER(PARTITION BY <..> ORDER BY <..>)`) | ||
| - [x] Custom Window (`ORDER BY time ROWS BETWEEN 2 PRECEDING AND 0 FOLLOWING)`) | ||
| - [x] User Defined Window and Aggregate Functions | ||
| - [x] Catalogs | ||
| - [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. Sorry @alamb that is not very clear to me. There was a problem hiding this comment. 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
3The 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. 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 |
||
| - [ ] `COPY .. INTO ..` | ||
| - [x] CSV | ||
| - [ ] JSON | ||
| - [ ] Parquet | ||
| - [ ] Avro | ||
|
|
||
| ## Runtime | ||
|
|
||
| - [x] Streaming Grouping | ||
|
There was a problem hiding this comment. I am not sure if there are other features to highlight in the RUNTIME |
||
| - [x] Streaming Window Evaluation | ||
| - [x] Memory limits enforced | ||
| - [x] Spilling (to disk) Sort | ||
| - [ ] Spilling (to disk) Grouping | ||
| - [ ] Spilling (to disk) Joins | ||
|
|
||
| ## Data Sources | ||
|
|
||
| In addition to allowing arbitrary datasources via the `TableProvider` | ||
| trait, DataFusion includes built in support for the following formats: | ||
|
|
||
| - [x] CSV | ||
| - [x] Parquet (for all primitive and nested types) | ||
| - [x] JSON | ||
| - [x] Avro | ||
| - [x] Arrow | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think this better reflects the current status:
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 agree.
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 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 👍