[
https://issues.apache.org/jira/browse/CASSANDRA-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856407#comment-17856407
]
Marcus Eriksson commented on CASSANDRA-18961:
---------------------------------------------
pushed an alternative patch
[here|https://github.com/apache/cassandra/pull/3380] which is less invasive -
it just stores the execution time in the {{AlterSchema}} transformation
> Record commit timestamp - fix data loss when dropping and recreating a column
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-18961
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18961
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
>
> Drop column transformation is replayed with the current timestamp so the
> column appears to be dropped when the node starts regardless of its real drop
> time.
> As a solution to this problem I propose recording the timestamp of the
> transformation, guaranteeing that it is always greater than a timestamp of
> any previously committed transformation. Such timestamp is passed to the
> execute method of the transformation so that the transformation code can make
> use of it, increasing its "purity".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
