[
https://issues.apache.org/jira/browse/CASSANDRA-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036186#comment-14036186
]
Benedict commented on CASSANDRA-6108:
-------------------------------------
It seems this implementation has some slightly weird behaviour: if more than
1000 timeuuids are produced in a single millisecond (potentially decoupled from
actually committing them to the database), updates from another client can get
overridden. Say a single client produces 100k updates before submitting them to
be processed asynchronously, these updates will create a 100ms window during
which any other client's writes will lose despite occurring later. This seems a
pretty dangerous tradeoff, and one user is likely to expect.
> Create timeid64 type
> --------------------
>
> Key: CASSANDRA-6108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6108
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.1.1
>
>
> As discussed in CASSANDRA-6106, we could create a 64-bit type with 48 bits of
> timestamp and 16 bites of unique coordinator id. This would give us a
> unique-per-cluster value that could be used as a more compact replacement for
> many TimeUUID uses.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
