[
https://issues.apache.org/jira/browse/CASSANDRA-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004756#comment-15004756
]
Tyler Hobbs commented on CASSANDRA-10694:
-----------------------------------------
Thanks, committed to 3.0 as {{c2320c92fdae6815b8952ba98b1e8e5239b5be2a}} and
merged to 3.1 and trunk.
There were some dtest failures on 3.0 and 3.1, but repeated manual runs of
relevant tests showed there weren't any issues. I'm not sure what was up with
all of the failed connections in the 3.1 dtests.
> Deletion info is dropped on updated rows when notifying secondary index
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-10694
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10694
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Fix For: 3.0.1, 3.1
>
> Attachments: index-deletion.patch
>
>
> In {{SecondaryIndexManager.onUpdated()}}, we fail to copy the
> {{DeletionInfo}} from the existing and new rows before notifying the index of
> the update. This leads the index to believe a new, live row has been
> inserted instead of a single-row deletion. It looks like this has been a
> problem since 3.0.0-beta1.
> I've attached a simple patch that fixes the issue. I'm working on a full
> patch with tests, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
