[
https://issues.apache.org/jira/browse/CASSANDRA-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-18457:
----------------------------------------
Fix Version/s: NA
Source Control Link:
https://github.com/apache/cassandra/commit/cd4f484fa0696f7faecf6cfb752cfb37ed391035
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> CEP-21 Ensure that SchemaTransformation impls correctly set TableMetadata
> epoch
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-18457
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18457
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: NA
>
>
> Many existing {{SchemaTransformation}} implementations (not to mention as yet
> unimplemented ones) have the potential to modify {{TableMetadata}} and it is
> brittle to require each of them to take care of updating the metadata epoch.
> We should have {{ClusterMetadata.Transformer}} or the {{AlterSchema}}
> transformation itself handle this automatically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
