[
https://issues.apache.org/jira/browse/CASSANDRA-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106541#comment-15106541
]
Marcus Eriksson commented on CASSANDRA-9949:
--------------------------------------------
I doubt it matters much which timestamp we pick there - this should happen very
rarely and when it does, there is not much harm (we keep some tombstones around
for a bit longer) so lets keep it consistent with the apply(Cell insert)
functionality
The 2.2-patch LGTM
> maxPurgeableTimestamp needs to check memtables too
> --------------------------------------------------
>
> Key: CASSANDRA-9949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9949
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths
> Reporter: Jonathan Ellis
> Assignee: Stefania
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> overlapIterator/maxPurgeableTimestamp don't include the memtables, so a
> very-out-of-order write could be ignored
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
