cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5487) Promote row-level tombstones to index file
Date Wed, 17 Apr 2013 21:55:16 GMT

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

Jonathan Ellis updated CASSANDRA-5487:
--------------------------------------

    Description: The idea behind promoted indexes (CASSANDRA-2319) was we could skip a seek
to the row header by keeping the column index in the index file.  But, we skip writing the
row-level tombstone to the index file unless it also has some column data.  So unless we read
the tombstone from the data file (where it is guaranteed to exist) we can return incorrect
results.  (was: The idea behind promoted indexes (CASSANDRA-2319) was we could skip a seek
to the row header by keeping the column index in the index file.  But, we left row-level tombstones
in the data file, so we still need to seek to read that.

A related note: IndexedSliceReader is some hellishly complex code.  If we can simplify that
at all, angels will weep tears of joy.)
    
> Promote row-level tombstones to index file
> ------------------------------------------
>
>                 Key: CASSANDRA-5487
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5487
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: Jonathan Ellis
>             Fix For: 2.0
>
>
> The idea behind promoted indexes (CASSANDRA-2319) was we could skip a seek to the row
header by keeping the column index in the index file.  But, we skip writing the row-level
tombstone to the index file unless it also has some column data.  So unless we read the tombstone
from the data file (where it is guaranteed to exist) we can return incorrect results.

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

Mime
View raw message