[
https://issues.apache.org/jira/browse/CASSANDRA-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495095#comment-13495095
]
Jonathan Ellis commented on CASSANDRA-4947:
-------------------------------------------
One use Brandon came up with for being able to specify timestamp client-side is
for recovering from a years-too-fast clock: issue deletes with sufficiently
high timestamps and compact the bad data out.
It would be more painful but we could still do this in theory with json2ssable.
Might be worth adding a JMX API to make it easier.
> 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
> Assignee: Sylvain Lebresne
> 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
