cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7297) semi-immutable CQL rows
Date Sat, 07 Nov 2015 10:57:11 GMT

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

Robert Stupp commented on CASSANDRA-7297:
-----------------------------------------

Is this "superseded" by CASSANDRA-9779?

> semi-immutable CQL rows
> -----------------------
>
>                 Key: CASSANDRA-7297
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7297
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Tupshin Harper
>              Labels: cql
>
> There are many use cases, where data is immutable at the domain model level. Most time-series/audit
trail/logging applications fit this approach.
> A relatively simple way to implement a bare-bones version of this would be to have a
table-level schema option for "first writer wins", so that in the event of any conflict, the
more recent version would be thrown on the floor.
> Obviously, this is not failure proof in the face of inconsistent timestamps, but that
is a problem to be addressed outside of Cassandra.
> Optional additional features could include logging any non-identical cells discarded
due to collision.



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

Mime
View raw message