Hi all,
are there plans to support geo-partitioning of data for YCQL as well?
Regards
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.
Please describe the use case in detail that needs TTL.