Lindorm is highly compatible with Cassandra Query Language (CQL), but some CQL features are unsupported or behave differently. Review these limits before migrating data from Apache Cassandra or building applications with the wide table engine.
Unsupported features
The following CQL features are not supported in Lindorm:
| Category | Feature | Notes |
|---|---|---|
| Data types | Collections | — |
| Data types | Duration | — |
| Data types | Counter | — |
| Schema | User-defined types (UDTs) | — |
| Schema | User-defined functions (UDFs) | — |
| Schema | User-defined aggregates (UDAs) | — |
| Schema | Materialized views | — |
| Schema | Triggers | — |
| Indexing | SSTable attached secondary indexes (SASI) | — |
| Data operations | Range deletes | — |
| Data operations | BATCH | — |
| Client behavior | Token-aware policy | — |
Behavioral differences
Timestamp precision
Apache Cassandra stores timestamps in microseconds. Lindorm stores timestamps in milliseconds.
Because a microsecond timestamp value is much larger than a millisecond timestamp value, Lindorm interprets microsecond timestamps as future timestamps. This may cause issues with time to live (TTL) expiration, data deletion, and data updates.
When migrating data from Apache Cassandra to a Lindorm wide table, exclude the writeTime column.
Further information
For limits not listed here, contact Lindorm technical support.