Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 27 Jun 2016 19:40:52 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12927067.1451938122000.8030.1467056452023@Atlassian.JIRA>
In-Reply-To: <JIRA.12927067.1451938122000@Atlassian.JIRA>
References: <JIRA.12927067.1451938122000@Atlassian.JIRA> <JIRA.12927067.1451938122889@arcas>
Subject: [jira] [Updated] (CASSANDRA-10965) Shadowable tombstones can
 continue to shadow view results when timestamps match
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 27 Jun 2016 19:40:53 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-10965:
---------------------------------------
    Status: Open  (was: Patch Available)

> Shadowable tombstones can continue to shadow view results when timestamps match
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10965
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10965
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>             Fix For: 3.0.x
>
>         Attachments: shadow-ts.cql
>
>
> I've attached a script which reproduces the issue. The first time we insert with {{TIMESTAMP 2}}, we are inserting a new row which has the same timestamp as the previous shadow tombstone, and it continues to be shadowed by that tombstone because we shadow values with the same timestamp.


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