Roadmap

Please note that the roadmap is intended to provide high-level visibility into the short-term direction of the product. This can change at any time.

2.1 Product Roadmap Highlights

Below you'll find the features we plan to deliver in the 2.1 release of CockroachDB. Note this does not include the work we are doing to improve performance and stability. Those efforts can be found in our GitHub.

CockroachDB Core Roadmap

SQL Updates

• Cost-based Query Optimizer - Provide orders of magnitude query speed-ups by using statistics to improve query plan selection.
• Correlated Subqueries - Support subquery that uses values from the outer query. Implementing this increases our support for more ORM functionality.
• Support Timetz Datatype - Increased SQL coverage to improve our drop-in compatibility with existing Hibernate applications
• support ALTER TABLE ... ALTER COLUMN ... SET DATA TYPE ... - Enable users and client apps to change the type of any column in a table.

Core Updates

• Load-based Splitting - Use per-replica load as an input for splitting a range.
• Read from follower with Timestamp Bound - Support consistent reads from a historical snapshot.

Troubleshooting & Supportability

• Track and report in-flight query execution stats - Add more stats in our existing tracing pathway to get more insight into how queries execute.
• Pause / resume / cancel schema changes via SQL - Manage schema change job lifecycle

Other

• Global/ multi-region Kubernetes cluster - Support running CockroachDB in a K8 cluster across multiple regions so that a developer can have a highly available application, low latency and fault isolation
• CockroachDB performance optimization on Kubernetes - Provide performance optimization suggestions to run CRDB in Kubernetes
• MySQL to CockroachDB via IMPORT -A fast and easy way to migrate from a mysql dump file to CockroachDB.

Web UI

• Allow users to identify bottlenecks in performance due to CPU / memory / IO / network issues - provide better visibility into how resources are being utilized so that users can plan for adequate hardware to meet their performance needs
• User Authentication - Implement basic login (authentication) that gives logged in users the ability to access the admin UI (rather than giving everyone with the URL root access).

Enterprise Roadmap

• Change Data Capture (CDC) - Support pushing database changes into Kafka rather than having to run periodic/polling jobs to pull data out.
• Distributed CSV Export - provide better visibility into how resources are being utilized so that users can plan for adequate hardware to hit their performance needs
• Encryption at Rest - Allow users to encrypt data on a per-store basis.
• Select foo Partition (p1) Syntax - Support querying data directly from a partition to improve performance.