[
https://issues.apache.org/jira/browse/CASSANDRA-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707394#comment-17707394
]
Andres de la Peña commented on CASSANDRA-18352:
-----------------------------------------------
I'm not sure the names of the properties match the style of other
{{cassandra.yaml}} properties. Usually the names of threshold guardrails
include the "_threshold" suffix.
For the case of min/max thresholds, we have the precedent of [the guardrail for
min/max replication
factor|https://github.com/apache/cassandra/blob/9f078090e9e07d0917716e395e770b766a327fc7/conf/cassandra.yaml#L1871-L1880],
which looks like:
{code:java}
minimum_replication_factor_warn_threshold
minimum_replication_factor_fail_threshold
maximum_replication_factor_warn_threshold
maximum_replication_factor_fail_threshold
{code}
If we follow the same naming style for consistency, the new yaml properties
would look like:
{code:java}
minimum_timestamp_warn_threshold
minimum_timestamp_fail_threshold
maximum_timestamp_warn_threshold
maximum_timestamp_fail_threshold
{code}
Instead of the current:
{code:java}
timestamp_warn_upper_bound
timestamp_fail_upper_bound
timestamp_warn_lower_bound
timestamp_fail_lower_bound
{code}
I don't see that we have any other properties whose names use lower/upper bound.
> Add Option to Timebox write timestamps
> --------------------------------------
>
> Key: CASSANDRA-18352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18352
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL/Semantics
> Reporter: Jordan West
> Assignee: Jordan West
> Priority: Normal
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
