-
Notifications
You must be signed in to change notification settings - Fork 753
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
Roadmap 2023 #9448
Comments
any plan about improving concurrency capabilities? so developers can depend on databend to make some data exploring platforms (like google analystics?) on the web. |
any plan about tuning the metasrv's memory usage? I've got a OOM last week, IMHO it can store most the data in the disk? |
Added: |
@drmingdrmer will fill the meta section, I think he will do it. |
Any plan to support |
Added to the main task, thanks. |
will fault tolerance on query processing be planned in 2023? likewise I have some spot instances, the cluster may handles a shutdowned instance gracefully and not affect the running queries. |
Will do but hard to do, so the priority is low.
Please file an issue for that. |
Is there a plan for when the vector index feature will be added? It is part of #10689 but doesn't seem to have an associated ticket. |
After a full year of research and development in 2022, the functionality and stability of Databend were significantly enhanced, and several users began using it in production. Databend has helped them greatly reduce costs and operational complexity issues.
This is Databend Roadmap in 2023 (discussion).
See also:
Main tasks
v1.3
v1.2 (Prepare for release on May 15th)
v1.1 (Prepare for release on April 5th)
v1.0 (Prepare for release on March 5th)
Features
Improvements
Planner
Cache
Data Storage
Distributed Query Execution
Resource Quota
Schema-Less Search
LakeHouse
Integrations
Meta
Testing
Releases
The text was updated successfully, but these errors were encountered: