Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CAAB9F093 for ; Tue, 2 Apr 2013 21:03:16 +0000 (UTC) Received: (qmail 94380 invoked by uid 500); 2 Apr 2013 21:03:16 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 94354 invoked by uid 500); 2 Apr 2013 21:03:16 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 94298 invoked by uid 99); 2 Apr 2013 21:03:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 21:03:16 +0000 Date: Tue, 2 Apr 2013 21:03:16 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (CASSANDRA-5397) Updates to PerRowSecondaryIndex don't use most current values MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5397: -------------------------------------- Comment: was deleted (was: What guard are you talking about? Have things changed since CASSANDRA-4458 was opened?) > Updates to PerRowSecondaryIndex don't use most current values > -------------------------------------------------------------- > > Key: CASSANDRA-5397 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5397 > Project: Cassandra > Issue Type: Bug > Affects Versions: 1.2.3 > Reporter: Sam Tunnicliffe > Assignee: Sam Tunnicliffe > Priority: Minor > Attachments: 5397.txt > > > The way that updates to secondary indexes are performed using SecondaryIndexManager.Updater is flawed for PerRowSecondaryIndexes. Unlike PerColumnSecondaryIndexes, which only require the old & new values for a single column, the expectation is that a PerRow indexer can be given just a key which it will use to retrieve the entire row (or as many columns as it requires) and perform its indexing on those columns. As the indexes are updated before the memtable atomic swap occurs, a per-row indexer may only read the previous values for the row, not the new ones that are being written. In the case of an insert, there is no previous value and so nothing is added to the index. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira