You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2024/06/20 07:34:00 UTC

[jira] [Updated] (CASSANDRA-18961) Record commit timestamp - fix data loss when dropping and recreating a column

     [ https://issues.apache.org/jira/browse/CASSANDRA-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-18961:
----------------------------------------
    Attachment: ci_summary.html

> 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
>         Attachments: ci_summary.html
>
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org