-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update Roadmap documentation #16399
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
Update Roadmap documentation #16399
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 |
---|---|---|
|
@@ -46,81 +46,12 @@ make review efficient and avoid surprises. | |
|
||
# Quarterly Roadmap | ||
|
||
A quarterly roadmap will be published to give the DataFusion community | ||
visibility into the priorities of the projects contributors. This roadmap is not | ||
binding and we would welcome any/all contributions to help keep this list up to | ||
date. | ||
The DataFusion roadmap is driven the priorities of the contributors rather than | ||
any single organization or coordinating committee. We typically discuss roadmap | ||
approximately quarterly in GitHub issues. | ||
|
||
## 2023 Q4 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. these items are quite old and I don't think they are serving much purpose anymore. Links to the more recent discussions I think are far more useful |
||
For more information: | ||
|
||
- Improve data output (`COPY`, `INSERT` and DataFrame) output capability [#6569](https://github.com/apache/datafusion/issues/6569) | ||
- Implementation of `ARRAY` types and related functions [#6980](https://github.com/apache/datafusion/issues/6980) | ||
- Write an industrial paper about DataFusion for SIGMOD [#6782](https://github.com/apache/datafusion/issues/6782) | ||
|
||
## 2022 Q2 | ||
|
||
### DataFusion Core | ||
|
||
- IO Improvements | ||
- Reading, registering, and writing more file formats from both DataFrame API and SQL | ||
- Additional options for IO including partitioning and metadata support | ||
- Work Scheduling | ||
- Improve predictability, observability and performance of IO and CPU-bound work | ||
- Develop a more explicit story for managing parallelism during plan execution | ||
- Memory Management | ||
- Add more operators for memory limited execution | ||
- Performance | ||
- Incorporate row-format into operators such as aggregate | ||
- Add row-format benchmarks | ||
- Explore JIT-compiling complex expressions | ||
- Explore LLVM for JIT, with inline Rust functions as the primary goal | ||
- Improve performance of Sort and Merge using Row Format / JIT expressions | ||
- Documentation | ||
- General improvements to DataFusion website | ||
- Publish design documents | ||
- Streaming | ||
- Create `StreamProvider` trait | ||
|
||
### Ballista | ||
|
||
- Make production ready | ||
- Shuffle file cleanup | ||
- Fill functional gaps between DataFusion and Ballista | ||
- Improve task scheduling and data exchange efficiency | ||
- Better error handling | ||
- Task failure | ||
- Executor lost | ||
- Schedule restart | ||
- Improve monitoring and logging | ||
- Auto scaling support | ||
- Support for multi-scheduler deployments. Initially for resiliency and fault tolerance but ultimately to support sharding for scalability and more efficient caching. | ||
- Executor deployment grouping based on resource allocation | ||
|
||
### Extensions ([datafusion-contrib](https://github.com/datafusion-contrib)) | ||
|
||
### [DataFusion-Python](https://github.com/datafusion-contrib/datafusion-python) | ||
|
||
- Add missing functionality to DataFrame and SessionContext | ||
- Improve documentation | ||
|
||
### [DataFusion-S3](https://github.com/datafusion-contrib/datafusion-objectstore-s3) | ||
|
||
- Create Python bindings to use with datafusion-python | ||
|
||
### [DataFusion-Tui](https://github.com/datafusion-contrib/datafusion-tui) | ||
|
||
- Create multiple SQL editors | ||
- Expose more Context and query metadata | ||
- Support new data sources | ||
- BigTable, HDFS, HTTP APIs | ||
|
||
### [DataFusion-BigTable](https://github.com/datafusion-contrib/datafusion-bigtable) | ||
|
||
- Python binding to use with datafusion-python | ||
- Timestamp range predicate pushdown | ||
- Multi-threaded partition aware execution | ||
- Production ready Rust SDK | ||
|
||
### [DataFusion-Streams](https://github.com/datafusion-contrib/datafusion-streams) | ||
|
||
- Create experimental implementation of `StreamProvider` trait | ||
1. [Search for issues labeled `roadmap`](https://github.com/apache/datafusion/issues?q=is%3Aissue%20%20%20roadmap) | ||
2. [DataFusion Road Map: Q3-Q4 2025](https://github.com/apache/datafusion/issues/15878) | ||
3[2024 Q4 / 2025 Q1 Roadmap](https://github.com/apache/datafusion/issues/13274) |
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.
should we define the way of
We typically discuss roadmap
? weekly meetings, slack, GH, etc?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.
From my perspective what happens today is we discuss roadmap for specific items on the related github tickets, and more generally on "Discussion" tickets once every quarter or two
I am not sure if you are suggesting we try and invest more effort into new / different processes.
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.
Nvm, I was just thinking it would be more clear to the reader to know where exactly the roadmap is discussed in case they want to participate as well.
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.
Thanks -- I tried to make it clearer and explicitly invited the reader to join the discussion