cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9917) MVs should validate gc grace seconds on the tables involved
Date Thu, 22 Jun 2017 16:37:00 GMT

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

Jeremy Hanna updated CASSANDRA-9917:
------------------------------------
    Component/s: Materialized Views

> 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
>          Components: Coordination, Materialized Views
>            Reporter: Aleksey Yeschenko
>            Assignee: Paulo Motta
>              Labels: docs-impacting, materializedviews
>             Fix For: 3.0 beta 2
>
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message