Docs: Update roadmap to point at EPIC's, clarify project goals #6639
Conversation
| @@ -132,7 +132,13 @@ | |||
| //! | |||
| //! ## Customization and Extension | |||
| //! | |||
| //! DataFusion supports extension at many points: | |||
| //! DataFusion is designed to be a "disaggregated" query engine. This | |||
There was a problem hiding this comment.
This is trying to address @boazberman 's comments in #6441 (comment)
| [Rust](https://www.rust-lang.org/) and [Apache Arrow](https://arrow.apache.org/) | ||
| to provide: | ||
|
|
||
| 1. Best-in-class single node query performance |
There was a problem hiding this comment.
These goals are largely redundant with the introduction, so I figured it would be better to leave a link and direct people back there rather than partially replicate the content
|
|
||
| ## Planning `EPIC`s | ||
|
|
||
| DataFusion uses [GitHub |
There was a problem hiding this comment.
I began this PR by trying to summarize the outstanding work and to do so I looked at the EPICs -- pretty soon I found that I was just replicating https://github.com/apache/arrow-datafusion/issues?q=is%3Aissue+is%3Aopen+epic in a markdown document that would end up out of date
While a more free form version of the roadmap in text (rather than a github issue list) is probably easier to consume, unless we have a volunteer to commit to doing, keeping our efforts focused on keeping github updated seemed better.
| building new systems. Here are some examples of systems built using DataFusion: | ||
| building new systems. | ||
|
|
||
| While most current usecases are "analytic" or (throughput) some |
There was a problem hiding this comment.
This is trying to channel @avantgardnerio 's suggestion on #6441 (comment) though I am not sure how faithfully I have done so
There was a problem hiding this comment.
I'm not sure I could say it any better.
There was a problem hiding this comment.
I don't think you need the or after "analytic" though?
There was a problem hiding this comment.
| While most current usecases are "analytic" or (throughput) some | |
| While most current usecases are "analytic" (throughput) some |
Nice catch -- 🦅 👁️
|
I plan to leave this PR open for a few more days to make sure anyone who is interested gets a chance to reply / comment. I'll try and merge it in towards the end of the week |
Which issue does this PR close?
Closes #3935
Related to #6441
Rationale for this change
Our roadmap is somewhat out of date as it refers to several projects that seem to have been completed (the relevant ticket have been closed)
Also, I am working on #5812 and wanted to have an up to date roadmap to discuss
Also, we recently had a discussion #6441 about the vision of DataFusion, which should be reflected in the user facing documentation
What changes are included in this PR?
Are these changes tested?
N/A
Are there any user-facing changes?