cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-3872) Sub-columns removal is broken in 1.1
Date Tue, 07 Feb 2012 16:57:02 GMT
Sub-columns removal is broken in 1.1
------------------------------------

                 Key: CASSANDRA-3872
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3872
             Project: Cassandra
          Issue Type: Bug
            Reporter: Sylvain Lebresne
            Assignee: Sylvain Lebresne


CASSANDRA-3716 actually broke sub-columns deletion. The reason is that in QueryFilter.isRelevant,
we've switched in checking getLocalDeletionTime() only (without looking for isMarkedForDelete).
But for columns containers (in this case SuperColumn), the default local deletion time when
not deleted is Integer.MIN_VALUE. In other words, a SC with only non-gcable tombstones will
be considered as not relevant (while it should).

This is caught by two unit tests (RemoveSuperColumnTest and RemoveSubColumnTest) that are
failing currently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message