[CASSANDRA-10261] Materialized Views Timestamp issues

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.0 rc1
• Component/s: Feature/Materialized Views, Legacy/Coordination
• Severity: Normal
• Assignee: T Jake Luciani
• Reporter: T Jake Luciani

Authors

T Jake Luciani

Reviewers

Tom Hobbs

• Created: 03/Sep/15 17:43
• Updated: 16/Apr/19 09:30
• Resolved: 11/Sep/15 15:41

Description

As thobbs mentioned 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.

Issue Links

• is related to: CASSANDRA-10368 Support Restricting non-PK Cols in Materialized View Select Statements
• relates to: CASSANDRA-13409 Materialized Views: View cells are resurrected