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

Jonathan Ellis updated CASSANDRA-5486:
--------------------------------------

    Description: 
Inspecting the read path for CASSANDRA-4180 reveals several bugs introduced by 
index promotion.  Most fall into two categories:

# Conflating RowIndexEntry.isIndexed with hasPromotedIndex (if the latter is 
true, we need to include its deletion info, even if there are no index entries, 
which is what the former refers to)
# Incorrectly assuming RowIndexEntry.deletionInfo is the entire DeletionInfo 
for the row, when it really only includes range tombstones

  was:
Inspecting the read path for CASSANDRA-4180 reveals several bugs introduced by 
index promotion.  Most fall into two categories:

# Incorrectly assuming that hasPromotedIndexes implies that the bloom filter is 
not present in the data file either
# Incorrectly assuming RowIndexEntry.deletionInfo is the entire DeletionInfo 
for the row, when it really only includes range tombstones

    
> bugs with index promotion and deletionInfo
> ------------------------------------------
>
>                 Key: CASSANDRA-5486
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5486
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 1.2.5
>
>
> Inspecting the read path for CASSANDRA-4180 reveals several bugs introduced 
> by index promotion.  Most fall into two categories:
> # Conflating RowIndexEntry.isIndexed with hasPromotedIndex (if the latter is 
> true, we need to include its deletion info, even if there are no index 
> entries, which is what the former refers to)
> # Incorrectly assuming RowIndexEntry.deletionInfo is the entire DeletionInfo 
> for the row, when it really only includes range tombstones

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

Reply via email to