Skip to content
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

Product Roadmap #2132

Closed
jess-edwards opened this issue Aug 17, 2015 · 9 comments

Comments

@jess-edwards
Copy link
Contributor

@jess-edwards jess-edwards commented Aug 17, 2015

Please note that this roadmap is only a look at features in development or still to come. It does not reflect the many features already completed by the CockroachDB community.

Beta roadmap

  • Rebalancing
    • Basic rebalancing support #620
    • Improved rebalancing heuristics #2600, #2747
  • Recovery #2149
  • Disable public KV access #2089
  • SQL
  • Stable on-disk format, wire protocols
  • Batches
  • Transaction cleanup #2062
  • Gob cleanup #629
  • Config prefix maps -> database / table descriptors #2090
  • Multiraft
  • Documentation
    • Table of contents
    • Quick start guide
    • Privileges #2134
    • Wire protocol
    • SQL grammar #2134
    • Deployment
    • Configuration
    • Troubleshooting
    • FAQ
  • Admin UI
    • Sufficient transient stats #2721
    • Aggregated graphs #2722
    • Aggregate error/warning log #2724
    • Application of design skin #2723
  • Prod / Deployment
    • Security #1675
    • Additional testing use cases #2432
    • Cloud-hosted cluster with load
    • Integrations #28
      • Digital Ocean

V 1.0

  • Response cache cleanup
  • Gossip cleanup / optimization
  • Backup / restore
  • Monitoring / alerting
  • Map reduce
  • Prod / Deployment
    • Integrations #28
      • Microsoft Azure
      • Openstack / Internap
  • SQL
    • Protobuf / JSON columns? #2969
    • Array type #2115
    • Decimal type #1618
    • Group by #2174
    • Having #2175
    • Joins #2970
    • Interleaved tables #2972
    • Foreign key constraints #2968
    • Performance
      • KV where clause support
    • Rich indexes
      • Geo spatial
      • Full text
  • Password-based authentication
  • Jepsen testing #4036
@joeblew99

This comment has been minimized.

Copy link

@joeblew99 joeblew99 commented Nov 22, 2015

Feature request: push queries.
I use these in rethinkdb because I have a streaming architecture with the compute and data in a large DAG.
It would be great if the concept of push queries was part of the features

@vivekmenezes

This comment has been minimized.

Copy link
Collaborator

@vivekmenezes vivekmenezes commented Nov 22, 2015

Joe,

We know that push queries are useful and they will hit the roadmap one day.
We are focusing a lot of our energy at the moment on performance and
stability. Thank you for your input, it is much appreciated.

Vivek

On Sun, Nov 22, 2015, 7:03 AM joeblew99 notifications@github.com wrote:

Feature request: push queries.
I use these in rethinkdb because I have a streaming architecture with the
compute and data in a large DAG.
It would be great if the concept of push queries was part of the features


Reply to this email directly or view it on GitHub
#2132 (comment)
.

@somecallmemike

This comment has been minimized.

Copy link

@somecallmemike somecallmemike commented Dec 7, 2015

I was wondering if there were any tentative timelines around the beta and V1 of CockroachDB? Looks like an amazing project and we want to start using it as soon as possible!

@vivekmenezes

This comment has been minimized.

Copy link
Collaborator

@vivekmenezes vivekmenezes commented Dec 8, 2015

Mike,

Thanks for your interest. We are working towards beta and are focused on
improving the performance and stability of the system. Unfortunately we
still do not have a confirmed beta date.

Thanks

On Mon, Dec 7, 2015, 5:25 PM somecallmemike notifications@github.com
wrote:

I was wondering if there were any tentative timelines around the beta and
V1 of CockroachDB? Looks like an amazing project and we want to start using
it as soon as possible!


Reply to this email directly or view it on GitHub
#2132 (comment)
.

@petermattis petermattis removed this from the Beta milestone Feb 29, 2016
@mbdas

This comment has been minimized.

Copy link

@mbdas mbdas commented Mar 11, 2016

Do you have any update on the beta date?

@spencerkimball

This comment has been minimized.

Copy link
Member

@spencerkimball spencerkimball commented Mar 17, 2016

@mbdas we expect to announce the beta very soon. In a small number of weeks. That will be the turning point for stability in the underlying data structures with an assured upgrade path.

@boreys

This comment has been minimized.

Copy link

@boreys boreys commented Mar 28, 2016

I hope to hear the good news soon. I have been watching this project for a long time now.

@spencerkimball

This comment has been minimized.

Copy link
Member

@spencerkimball spencerkimball commented Mar 30, 2016

@petermattis need to close this issue and start a new one...

@petermattis

This comment has been minimized.

Copy link
Contributor

@petermattis petermattis commented Mar 30, 2016

Yep. Closing this for now. I'm going to work on a revamped 1.0 roadmap in the next week or so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.