[
https://issues.apache.org/jira/browse/CASSANDRA-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451169#comment-17451169
]
Benjamin Lerer edited comment on CASSANDRA-17048 at 12/3/21, 9:07 AM:
----------------------------------------------------------------------
One problem I see is with the current patch is that the existing tests will not
check the use of the new identifier but the use of the old one.
We also probably need to also check the transistion from the sequential one to
the UUID one.
was (Author: blerer):
On problem, I see is with the current patch is that the existing tests will not
check the use of the new identifier but the use of the old one.
We also probably need to also check the transistion from the sequential one to
the UUID one.
> Replace sequential sstable generation identifier with UUID v1
> -------------------------------------------------------------
>
> 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
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
