[CASSANDRA-18352] Add Option to Timebox write timestamps

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0, 5.0-alpha1
• Component/s: CQL/Semantics
• Change Category: Semantic
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/2ff1ad4788a1e29b99f81f75b2966b7951ba8250

Test and Documentation Plan

Added 2 new tests

• Assignee: Jordan West
• Reporter: Jordan West

Authors

Jordan West

Reviewers

Andres de la Peña, Brandon Williams

• Created: 21/Mar/23 07:07
• Updated: 12/Sep/23 13:03
• Resolved: 17/May/23 20:35

Description

In several cases it is desirable to have client provided timestamps generated at the application-level. This can be error prone, however. In particular, applications can choose timestamps that may be nonsensical for a given application. One dangerous manifestation of this is the "doomstone" (a tombstone far in the future of any realistic write). This feature would allow either operators or users to specify a minimum and maximum timebound of "reasonable" timestamps. The default would be negative infinity, positive infinity to maintain backwards compatibility. Writes that are USING TIMESTAMP with a timestamp outside of the timebox will see an exception.

Issue Links

• is duplicated by: CASSANDRA-18374 Create a guardrail to prevent writing of timestamps in the distant future
• links to: GitHub Pull Request #2246