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-8527) Extend tombstone_warning_threshold to range tombstones
Date Thu, 12 Mar 2015 08:11:39 GMT

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

Aleksey Yeschenko commented on CASSANDRA-8527:
----------------------------------------------

I'm not sure that changing the current behaviour in a minor release is something we can do
safely. For one, some people's queries will suddenly and unexpectedly stop working, for two,
it's a small, but non-trivial enough change for a minor, code-wise.

As for 3.0, should get CASSANDRA-8099 in first, assuming that it doesn't handle this already.

Either way, relabeling as 3.0 for now.

> Extend tombstone_warning_threshold to range tombstones
> ------------------------------------------------------
>
>                 Key: CASSANDRA-8527
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8527
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.0
>
>
> As discussed in CASSANDRA-8477, we should make sure the tombstone thresholds also apply
to range tombstones, since they poses the same problems than cell tombstones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message