You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jon Haddad (JIRA)" <ji...@apache.org> on 2018/02/08 19:05:00 UTC
[jira] [Updated] (CASSANDRA-8527) Account for range tombstones
wherever we account for tombstones
[ https://issues.apache.org/jira/browse/CASSANDRA-8527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Haddad updated CASSANDRA-8527:
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.x)
4.0
3.11.2
Reproduced In: 3.11.1 (was: 3.11.1, 4.x)
Status: Resolved (was: Patch Available)
Merged into trunk as {{b2d20d4bb1}} and 3.11.2 as {{9d649d69a5}}.
> Account for range tombstones wherever we account for tombstones
> ---------------------------------------------------------------
>
> Key: CASSANDRA-8527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8527
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Alexander Dejanovski
> Priority: Major
> Fix For: 3.11.2, 4.0
>
> Attachments: CASSANDRA-8527-4.x.diff
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org