[
https://issues.apache.org/jira/browse/CASSANDRA-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042286#comment-13042286
]
Jonathan Ellis commented on CASSANDRA-2621:
-------------------------------------------
It sounds like the only bug here is the one described in CASSANDRA-2590, is
that right?
> sub columns under deleted CF returned
> --------------------------------------
>
> Key: CASSANDRA-2621
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2621
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.5, 0.8.0 beta 2
> Reporter: Aaron Morton
> Assignee: Aaron Morton
> Priority: Minor
>
> found when working on CASSANDRA-2590
> In some cases sub columns are not filtered to check if they have a higher
> timestamp than and container super column or CF. For example a super col with
> two two columns, one with timestamp 0 and the other 5, will be returned with
> all columns even if there is a row delete at timestamp 2.
> If the QueryFilter is created with a null superColumnName in the QueryPath it
> will not filter the sub columns.
> IdentityQueryFilter.filterSuperColumn() lets all sub columns through.
> NamesQueryFilter.filterSubColumn() and SliceQueryFilter() check that each sub
> column is relavent.
> I have a fix and am working on some test cases.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
