You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/09/18 18:37:04 UTC
[jira] [Commented] (CASSANDRA-10174) Range tombstones through
thrift don't handle static columns probably
[ https://issues.apache.org/jira/browse/CASSANDRA-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875919#comment-14875919 ]
Sylvain Lebresne commented on CASSANDRA-10174:
----------------------------------------------
I've started looking at this and I'll make sure to finish that before 3.0 GA, but "range deletion through thrift on a CQL table with static columns" is a sufficiently obscure case that it's not worth blocking RC1.
> Range tombstones through thrift don't handle static columns probably
> --------------------------------------------------------------------
>
> Key: CASSANDRA-10174
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10174
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 3.0.x
>
>
> When inserting range tombstones through thrift in a "static" compact table, the current code doesn't properly delete the static components of the table (even when it should).
> To the best of my knowledge, we don't have a test for this (though in all fairness, range deletions through thrift is a pretty late addition and has little coverage) so the first step will probably be to reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)