cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4947) Disallow client-provided timestamps in cql3
Date Wed, 14 Nov 2012 05:20:16 GMT


Edward Capriolo commented on CASSANDRA-4947:

-1 there are people out there using different conventions.
Timestamps can be anything you like, but microseconds since 1970 is a convention. Whatever
you use, it must be consistent across the application, otherwise earlier changes may overwrite
newer ones. 

You can't unring a bell.  
> Disallow client-provided timestamps in cql3
> -------------------------------------------
>                 Key: CASSANDRA-4947
>                 URL:
>             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:

View raw message