Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 29 Jul 2015 12:34:05 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12849921.1438173214000.318471.1438173245191@Atlassian.JIRA>
In-Reply-To: <JIRA.12849921.1438173214000@Atlassian.JIRA>
References: <JIRA.12849921.1438173214000@Atlassian.JIRA>
 <JIRA.12849921.1438173214346@arcas>
Subject: [jira] [Created] (CASSANDRA-9917) MVs should validate gc grace
 seconds on the tables involved
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-9917:
--------------------------------------------

             Summary: MVs should validate gc grace seconds on the tables involved
                 Key: CASSANDRA-9917
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9917
             Project: Cassandra
          Issue Type: Bug
            Reporter: Aleksey Yeschenko
            Assignee: T Jake Luciani
             Fix For: 3.0 beta 1


For correctness reasons (potential resurrection of dropped values), batchlog entries are TTLs with the lowest gc grace second of all the tables involved in a batch.

It means that if gc gs is set to 0 in one of the tables, the batchlog entry will be dead on arrival, and never replayed.

We should probably warn against such LOGGED writes taking place, in general, but for MVs, we must validate that gc gs on the base table (and on the MV table, if we should allow altering gc gs there at all), is never set too low, or else.


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