Hi all,
are there plans to support geo-partitioning of data for YCQL as well?
Regards
Hi @beatrausch
There is not in near-term roadmap.
Any reason you can’t use YSQL for this?
Basically we decided to use YCQL because of the following reasons based on your FAQ:
- TTL-driven automatic data expiration.
- Integration with stream processors, such as Apache Spark and KSQL.
- Serve low-latency (sub-millisecond) queries.
@dorian_yugabyte I would say the main blocking point is the missing TTL feature of YSQL
Please describe the use case in detail that needs TTL.