cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1571) Secondary Indexes aren't updated when removing whole row
Date Tue, 05 Oct 2010 17:06:38 GMT


Stu Hood commented on CASSANDRA-1571:

* ColumnFamilyStoreTest uses deletion.value() to confirm that the value was actually removed,
but a column that has been deleted and GCd does not contain the original column: the original
column contained 'x0000000000000001' and the deletion contains 'x4cab5aad'
* In Table.ignoreObsoleteMutations, is there a way to avoid cloning the CF for each column?
Perhaps adding all columns to a single clone, and then collecting them back out?
* Can you add a quickie Javadoc to explain the readCurrent, ignoreObsolete and applyIndex

> Secondary Indexes aren't updated when removing whole row
> --------------------------------------------------------
>                 Key: CASSANDRA-1571
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Petr Odut
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.0
>         Attachments: 1571.txt
> When I remove a whole row in a CF
> del SomeColumnFamily['row']
> SI is not updated and get_indexed_slices still returns the deleted row.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message