Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 13 Nov 2015 15:15:11 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12912547.1447350689000.62448.1447427711312@Atlassian.JIRA>
In-Reply-To: <JIRA.12912547.1447350689000@Atlassian.JIRA>
References: <JIRA.12912547.1447350689000@Atlassian.JIRA>
 <JIRA.12912547.1447350689132@arcas>
Subject: [jira] [Updated] (CASSANDRA-10694) Deletion info is dropped on
 updated rows when notifying secondary index
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko updated CASSANDRA-10694:
------------------------------------------
    Component/s: Local Write-Read Paths

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