[ https://issues.apache.org/jira/browse/CASSANDRA-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040527#comment-14040527 ]
Benedict commented on CASSANDRA-6108: ------------------------------------- How do we safely manage the life cycle of the ids? We have no idea if the client is still alive or not > 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)