You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/29 04:32:24 UTC

[jira] [Commented] (CASSANDRA-6108) Create timeid64 type

    [ https://issues.apache.org/jira/browse/CASSANDRA-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781216#comment-13781216 ] 

Jonathan Ellis commented on CASSANDRA-6108:
-------------------------------------------

Pushed a sketch of an implementation to https://github.com/jbellis/cassandra/commits/6108.

I created a generic Sequences implementation since that seems like it will also be useful to expose to users, with the usual Paxos disclaimers.

I have not tried to wire this up to CQL.

(Note that the coordinator id is the least-significant bytes, which allows easily comparing timeid64s as longs without having to do bitmasking tricks.)

> 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
>
>
> 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.1#6144)