You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2023/04/18 09:45:00 UTC
[jira] [Created] (CASSANDRA-18460) CEP-21 Ensure that ClusterMetadata::forceEpoch keeps component epochs consistent
Sam Tunnicliffe created CASSANDRA-18460:
-------------------------------------------
Summary: CEP-21 Ensure that ClusterMetadata::forceEpoch keeps component epochs consistent
Key: CASSANDRA-18460
URL: https://issues.apache.org/jira/browse/CASSANDRA-18460
Project: Cassandra
Issue Type: Improvement
Components: Transactional Cluster Metadata
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
{{forceEpoch}} is used to make the application of multiple transformations in series appear as a single atomic update. It's primary use is in {{UnsafeJoin}} (i.e. join without bootstrap) to apply the usual sequence of start/mid/finish join in a single transformation. In such cases, we must ensure that no component of {{ClusterMetadata}} which maintains its own last-modified epoch, ends up with an epoch greater than the one of the enclosing {{ClusterMetadata}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org