[
https://issues.apache.org/jira/browse/CASSANDRA-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431336#comment-17431336
]
Benedict Elliott Smith edited comment on CASSANDRA-17048 at 10/20/21, 4:06 PM:
-------------------------------------------------------------------------------
I think human readable timestamps are actually pretty illegible when they are
very long, which they probably would be here. But perhaps this would still be
better. We could perhaps go for a human readable timestamp down to the seconds
granularity, and base32/36 for the remainder? We could perhaps even decompose
the date and intra-day timestamp, as this would make human parsing much easier.
was (Author: benedict):
I think human readable timestamps are actually pretty illegible when they are
very long, which they probably would be here. But perhaps this would be better.
We could perhaps go for a human readable timestamp down to the seconds
granularity, and base32/36 for the remainder? We could perhaps even decompose
the date and intra-day timestamp, as this would make human parsing much easier.
> 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]
