[jira] [Commented] (CASSANDRA-10694) Deletion info is dropped on updated rows when notifying secondary index

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002558#comment-15002558 ] 

Tyler Hobbs commented on CASSANDRA-10694:
-----------------------------------------

Like CASSANDRA-10690, this also doesn't visibly affect the built-in secondary indexes due to stale entry handling, although it would eventually have an impact on performance if a lot of deletions are performed on indexed data.  However, for custom secondary indexes, this is problematic.

> 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: index
>            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)