Product Roadmap

[jess-edwards]

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 Rebalance range replica. Only fully-replicated ranges may be rebalanced. #620
  • Improved rebalancing heuristics rebalancing: Rebalancing criteria is not effective for nodes running on the same machine #2600, storage: evaluate improved rebalancing heuristics #2747
• Recovery Recovery / Repairing #2149
• Disable public KV access lock down KV endpoints #2089
• SQL
  • Single table queries
  • Support for indexes sql: analyze where conditions to avoid full table scans in SELECT #1625, sql: support "point" lookups using indexes #2140, sql: better query planning for OR expressions #2142
  • Transactions sql: support BEGIN, ABORT, COMMIT transaction #1890, SQL transaction restart behavior #2094
  • Builtin functions sql/parser: flesh out the support for functions #2042
  • Aggregation functions (e.g. COUNT()) sql/parser: add support for aggregate functions #2043
  • Order By sql: add support for ORDER BY #2096, sql: utilize reverse scans when useful for ORDER BY #2169
  • Permissions / privileges sql: use real privileges instead of READ|WRITE #2005
  • Schema change sql: asynchronous ALTER TABLE name [ADD|DROP] COLUMN ... #2035, sql: asynchronous [CREATE|DROP] INDEX #2036
  • Schema distribution RFC: Gossip the schema #1743
  • Support DATE and TIMESTAMP columns sql: support TIMESTAMP and DATE column types #1995, sql: Implement SET TIME ZONE #2327, sql: Add DATE/TIMESTAMP/INTERVAL parameters #2328, sql: Add useful Date/Timestamp functions. #2329
  • Update grammar with modern amenities
  • Postgres-compatible server endpoint sql: postgres-compatible endpoint #2720
• Stable on-disk format, wire protocols
  • RPC version rpc: RPC versions #2719
  • RocksDB storage version storage/engine: add version number in rocksdb directory #2718
• Batches
  • Store-side Replica Batch ground work #2340
  • Dist sender coordinator batching #2406 implement gateway batch RFC #2130
  • 1PC txns 1PC transactions #2716, Re-enable auto-gc for one-shot transactions #2717
• Transaction cleanup GC of Transaction table #2062
• Gob cleanup Change Gossip to send only protobufs #629
• Config prefix maps -> database / table descriptors Make configs aware of structured data layout #2090
• Multiraft
  • Stability / correctness raft: NPE in TestRaftAfterRemoveRange #1911 raft: panic: applied(25) is out of range [prevApplied(10), committed(10)] #1878 raftLog.term Panic #1488 Range created by Split may conflict with Range created by multiraft #1644 crash when a replica remove itself from raft group #1650 Reject ProposeRaftCommand from removed replicas #1972
  • Tombstones Range replica removal #768
  • Optimization After range splitting, the newly created range take near 2 seconds to accept command. #1384 Raft stuck on writing hard state #1573
• Documentation
  • Table of contents
  • Quick start guide
  • Privileges Document SQL commands. #2134
  • Wire protocol
  • SQL grammar Document SQL commands. #2134
  • Deployment
  • Configuration
  • Troubleshooting
  • FAQ
• Admin UI
  • Sufficient transient stats ui: implementation of transient stats for admin UI #2721
  • Aggregated graphs ui: aggregrated graphs in admin UI #2722
  • Aggregate error/warning log ui: aggregate error/warning table and corresponding admin UI #2724
  • Application of design skin Application of design UI Kit to Admin UI #2723
• Prod / Deployment
  • Security security: cert deployment #1675
  • Additional testing use cases Testing Use Cases #2432
  • Cloud-hosted cluster with load
  • Integrations Check if phabricator plays nicely with github issues #28
    • Digital Ocean

V 1.0

• Response cache cleanup
• Gossip cleanup / optimization
• Backup / restore
• Monitoring / alerting
• Map reduce
• Prod / Deployment
  • Integrations Check if phabricator plays nicely with github issues #28
    • Microsoft Azure
    • Openstack / Internap
• SQL
  • Protobuf / JSON columns? sql: support JSON/Protobuf #2969
  • Array type sql: add support for ARRAY type #2115
  • Decimal type sql: add support for decimal arithmetic #1618
  • Group by sql: add support for GROUP BY #2174
  • Having sql: add support for HAVING #2175
  • Joins sql: support JOIN #2970
  • Interleaved tables sql: support interleaved tables #2972
  • Foreign key constraints sql: support FOREIGN KEY constraints #2968
  • Performance
    • KV where clause support
  • Rich indexes
    • Geo spatial
    • Full text
• Password-based authentication
• Jepsen testing Implement Jepsen testing for CockroachDB #4036

[joeblew99]

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]

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 [email protected] 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]

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]

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 [email protected]
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)
.

[mbdas]

Do you have any update on the beta date?

[spencerkimball]

@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]

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

[spencerkimball]

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

[petermattis]

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