[
https://issues.apache.org/jira/browse/CASSANDRA-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict Elliott Smith updated CASSANDRA-15431:
-----------------------------------------------
Fix Version/s: 4.x
> add table options required_ttl and max_ttl
> ------------------------------------------
>
> Key: CASSANDRA-15431
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15431
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair, Legacy/Local Write-Read Paths,
> Local/Compaction
> Reporter: David Capwell
> Priority: Normal
> Fix For: 4.x
>
>
> This is related to CASSANDRA-9420
> For use cases where applications know an upper bound on TTL or know that all
> TTLs are the same value, if this is put into the schema then we can choose to
> skip cells past these TTL values rather than converting them to tombstones.
> For this to work, we would need these fixed and immutable once set into the
> table, but would need to allow tables to add this after the fact (alter
> table).
> For all new data, the TTLs would need to be checked to make sure that they
> respect the expected property (the ttl is required_ttl if defined, or <=
> max_ttl if defined). For existing data, we could ether validate the TTL
> matches the expected setting and drop the cell, or we could detect that it
> doesn’t match, and fall back to tombstone (see
> org.apache.cassandra.db.rows.AbstractCell#purge).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
