[
https://issues.apache.org/jira/browse/CASSANDRA-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703013#comment-14703013
]
Paulo Motta commented on CASSANDRA-9917:
----------------------------------------
Updated patch available for review
[here|https://github.com/apache/cassandra/compare/cassandra-3.0...pauloricardomg:9917-3.0-v2]
Tests updated: [cassandra-dtest
PR|https://github.com/riptano/cassandra-dtest/pull/478]
Tests will appear shortly in the links below:
* [3.0
dtests|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9917-3.0-v2-dtest/]
* [3.0
testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9917-3.0-v2-testall/]
* [trunk
dtests|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9917-trunk-v2-dtest/]
* [trunk
testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9917-trunk-v2-testall/]
> 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 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.3.4#6332)
