[
https://issues.apache.org/jira/browse/CASSANDRA-18954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837173#comment-17837173
]
Jacek Lewandowski commented on CASSANDRA-18954:
-----------------------------------------------
[~samt] - CASSANDRA-12937 problem is caused by the fact that the
transformations are not pure. It is not enough that they are side-effects-free,
they also cannot depend on any external properties other than the current
cluster state and the store transformation data. I haven't looked at the fixed
you mentioned, but in my PR there was just an example fix for one schema
transformation - alter-table, one of the applied fixes was to not verify
"enableDropCompactStorage" from the configuration in replay mode because the
configuration is not the part of the transformation data. That could lead to
different outcomes after replaying a log, in particular to inability to start
the cluster after changing the configuration.
> Transformations should be pure so that replaying them results in the same
> outcome regardless of the node state or configuration
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18954
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
>
> Discussed on Slack
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
