cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5435) Support range tombstones from thrift
Date Thu, 11 Apr 2013 16:27:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629074#comment-13629074
] 

Aleksey Yeschenko commented on CASSANDRA-5435:
----------------------------------------------

I don't care deeply about thrift or supercolumns, but, if we are going to add this, this should
be done right: when super_column is set, slice range should refer to the subcolumns - it's
trivial to implement with composites.

The test in the first commit is sort of useless. As for the test from the second commit -
I'd rather see it in cassandra-dtest. Also should add a test for non-null super_column+slice
range.
                
> Support range tombstones from thrift
> ------------------------------------
>
>                 Key: CASSANDRA-5435
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5435
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Edward Capriolo
>            Assignee: Edward Capriolo
>            Priority: Minor
>
> I see a RangeTomstone test and methods in row mutation. However thrift's validate method
throws exception when Deletion's have a slice predicate. 

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