You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tupshin Harper (JIRA)" <ji...@apache.org> on 2014/05/24 21:26:01 UTC
[jira] [Created] (CASSANDRA-7297) semi-immutable CQL rows
Tupshin Harper created CASSANDRA-7297:
-----------------------------------------
Summary: semi-immutable CQL rows
Key: CASSANDRA-7297
URL: https://issues.apache.org/jira/browse/CASSANDRA-7297
Project: Cassandra
Issue Type: Improvement
Components: API, Core
Reporter: Tupshin Harper
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.2#6252)