[jira] [Updated] (CASSANDRA-20828) When a table is writing to accord and the mutation is a regular CQL mutation, if a multi cell list was written the cell path's timestamp did not reflect the transaction timestamp

["David Capwell (Jira)" <ji...@apache.org>]

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

David Capwell updated CASSANDRA-20828:
--------------------------------------
    Status: Open  (was: Patch Available)

> When a table is writing to accord and the mutation is a regular CQL mutation, if a multi cell list was written the cell path's timestamp did not reflect the transaction timestamp
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20828
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20828
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Accord
>            Reporter: David Capwell
>            Priority: Normal
>             Fix For: 6.x
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When a list type is written in CAS or BEGIN TRANSACTION we have a custom Updater that defines what the cell path should be for the list type, but when you used regular CQL we fall back to wall clock time.  We normally allow this in accord as we rewrite the timestamps during the write phase but the list cell path was not updated



--
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