[
https://issues.apache.org/jira/browse/CASSANDRA-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434222#comment-17434222
]
Benedict Elliott Smith commented on CASSANDRA-17048:
----------------------------------------------------
If we take option (5) I don't think we ever need a downgrader tool? Folk who
begin using new sstable generation ids cannot downgrade past the point at which
they enable the feature (which is probably fine, but also a downgrader for this
would be a pretty easy tool to write in a pinch), but since all of the int
generations continue to be written to the same system table there's essentially
no effect for most users on upgrade?
bq. I tried to just "rename" system keyspace migrator, but given to the amount
of changes git decided to remove/add it
Ah, that would explain it. I was just looking at the diff, not closely at the
details just yet.
> 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
>
> Time Spent: 20m
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
