[
https://issues.apache.org/jira/browse/CASSANDRA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262809#comment-13262809
]
Robert Coli commented on CASSANDRA-1983:
----------------------------------------
+1 here, global uniqueness for sstable names would make many copy-the-sstables
style maint operations easier, as you wouldn't have to manually resolve the
namespace conflict. just now I saw someone in #cassandra who was setting up a
cluster with a copy of data get confused by non-unique filenames being
overwritten on his new cluster. the only downside seems to be longer sstable
file names.
> Make sstable filenames contain a UUID instead of increasing integer
> -------------------------------------------------------------------
>
> Key: CASSANDRA-1983
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1983
> Project: Cassandra
> Issue Type: Improvement
> Reporter: David King
> Priority: Minor
>
> sstable filenames look like CFName-1569-Index.db, containing an integer for
> uniqueness. This makes it possible (however unlikely) that the integer could
> overflow, which could be a problem. It also makes it difficult to collapse
> multiple nodes into a single one with rsync. I do this occasionally for
> testing: I'll copy our 20 node cluster into only 3 nodes by copying all of
> the data files and running cleanup; at present this requires a manual step of
> uniqifying the overlapping sstable names. If instead of an incrementing
> integer, it would be handy if these contained a UUID or somesuch that
> guarantees uniqueness across the cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
