Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 8 Sep 2015 21:19:46 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12861630.1441302224000.283630.1441747186253@Atlassian.JIRA>
In-Reply-To: <JIRA.12861630.1441302224000@Atlassian.JIRA>
References: <JIRA.12861630.1441302224000@Atlassian.JIRA>
 <JIRA.12861630.1441302224091@arcas>
Subject: [jira] [Commented] (CASSANDRA-10261) Materialized Views Timestamp
 issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tyler Hobbs commented on CASSANDRA-10261:
-----------------------------------------

I haven't given this a thorough review yet, but as quick feedback:
* The serialization changes aren't backwards-compatible.  They need to be conditional on {{version}}.
* I'd go with Sylvain's suggestion of {{isWeak}} for the name on the flag.
* It would be good to add base-table deletions to the mix in your unit test, where possible.

I should have more complete feedback shortly.

> Materialized Views Timestamp issues
> -----------------------------------
>
>                 Key: CASSANDRA-10261
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10261
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0.0 rc1
>
>
> As [~thobbs] [mentioned|https://issues.apache.org/jira/browse/CASSANDRA-9664?focusedCommentId=14724150&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14724150] in CASSANDRA-9664 there are issues dealing with updates to individual cells which can mask data from the base table in the view when trying to filter data correctly in the view.  
> Unfortunately, this same issue exists for all MV tables with regular columns.
> In the earlier versions of MV we did have a fix for this which I now can see is ineffective for all situations.
> I've pushed some unit tests to show the issue (similar to tylers) and a fix.  The idea is we keep the base table's timestamps per cell as it so we can *always* tell (per replica) which version of the record is the latest.  Since the base table *always* writes the entire record to the view (part of our earlier partial fix) we can ensure the view record contains *at least* views primary key timestamp.  


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