cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9917) MVs should validate gc grace seconds on the tables involved
Date Thu, 13 Aug 2015 19:17:46 GMT

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

Paulo Motta commented on CASSANDRA-9917:
----------------------------------------

so, if I understood correctly, we want to validate on CreateMVStatement if baseTable.gcGraceSeconds
< MIN_GC_GRACE_SECONDS, and also on AlterTableStatement if baseTable.NewGcGraceSeconds
< MIN_GC_GRACE_SECONDS, is that correct? I will assume this is the case, please let me
know if I should validate in the actual write instead.

> 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: Paulo Motta
>              Labels: materializedviews
>             Fix For: 3.0.0 rc1
>
>
> 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)

Mime
View raw message