[ https://issues.apache.org/jira/browse/CASSANDRA-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430600#comment-17430600 ]
Jeremiah Jordan commented on CASSANDRA-17048: --------------------------------------------- I think this is a great change. sstables version number clash has always been an issue when backing up and restoring tables. There was just a conversation the other day in the slack where a truncate of a table and then restart cause the sstables numbers to reset, which then messed up someone’s backups. > Replace sequential sstable generation identifier with ULID > ---------------------------------------------------------- > > Key: CASSANDRA-17048 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17048 > Project: Cassandra > Issue Type: Improvement > Components: Local/SSTable > Reporter: Jacek Lewandowski > Assignee: Jacek Lewandowski > Priority: Normal > Fix For: 4.1 > > > Replace the current sequential sstable generation identifier with ULID based. > ULID is better because we do not need to scan the existing files to pick the > starting number as well as we can generate globally unique identifiers. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org