cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-5397) Updates to PerRowSecondaryIndex don't use most current values
Date Thu, 04 Apr 2013 15:57:16 GMT


Jonathan Ellis updated CASSANDRA-5397:

    Attachment: 5397-1.2-v3.txt

v3 against 1.2 fixes some formatting and removes the {{if (column.isMarkedForDelete()) return}}
from MIU.update, since it would re-introduce one of the problems fixed in CASSANDRA-5395.

Not sure if it should actually be moved to the "not instanceof PCSI" block -- if so, how does
PRSI remove stale entries?
> Updates to PerRowSecondaryIndex don't use most current values 
> --------------------------------------------------------------
>                 Key: CASSANDRA-5397
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>         Attachments: 5397_12.txt, 5397-1.2-v3.txt, 5397_trunk.txt, 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:

View raw message