cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4947) Disallow client-provided timestamps in cql3
Date Mon, 12 Nov 2012 14:45:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-4947.
---------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Sylvain Lebresne)

Ben Coverston: "Client provided timestamps are helpful if a write fails and you want to "replay"
the writes later."

Sylvain: "I remember having used once a client timestamp in a hand-made 'repair' job, where
I "repaired" some denormalized table from the data of another one, and setting the timestamp
manually was useful to make I wasn't breaking stuff due to a concurrent/newer update."
                
> Disallow client-provided timestamps in cql3
> -------------------------------------------
>
>                 Key: CASSANDRA-4947
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4947
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Jonathan Ellis
>            Priority: Blocker
>             Fix For: 1.2.0
>
>
> Client-provided timestamps cause a lot of pain since we can't make any assumptions as
to client:server clock agreement.  Is this worth the pain?  If not we should rip out {{WITH
TIMESTAMP}} before 1.2.0. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message