[
https://issues.apache.org/jira/browse/CASSANDRA-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Hanna updated CASSANDRA-13214:
-------------------------------------
Component/s: Materialized Views
> Data versioning for rows
> ------------------------
>
> Key: CASSANDRA-13214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13214
> Project: Cassandra
> Issue Type: Improvement
> Components: Local Write-Read Paths, Materialized Views
> Reporter: Bhuvan Rawal
> Fix For: 4.x
>
>
> Row level data versioning can be implemented in cassandra in two possible
> ways :
> 1. Specify the last clustering column as a timestamp and all the previous
> data is merged into latest one. User can specify versioning while creating
> the table.
> 2. Create a materialized view with last column as timestamp without really
> touching the base table. Although a bit different from traditional MV as here
> it will contain data as versioned and in MV read before write complete
> partition data can be sent.
> This will help people maintain historical records versioned without current
> client level challenges - consistency challenges etc, and rather doing at
> server level using things already implemented in place at cassandra level -
> materialized views, partition locks for MV update.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
