You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 05:32:01 UTC
[jira] [Updated] (CASSANDRA-11160) Use UUID for SS Table Filenames
[ https://issues.apache.org/jira/browse/CASSANDRA-11160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-11160:
-----------------------------------------
Component/s: Local Write-Read Paths
> Use UUID for SS Table Filenames
> -------------------------------
>
> Key: CASSANDRA-11160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11160
> Project: Cassandra
> Issue Type: Improvement
> Components: Local Write-Read Paths
> Reporter: Anubhav Kale
> Priority: Minor
>
> Today, Cassandra uses monotonically increasing counter to generate SS Table file names. While this works practically, wouldn't it be safer / better if UUIDs are used in file names to make them really unique ? AFAIK, no code paths rely on such counters being part of files.
> A specific scenario where this will really help is below:
> In backup / restore model, suppose we move files out to some other storage. In that process, we can optimize by not moving files that were already backed up using a check on file names (which we can't do easily today because if the node went down, a file with same name can be generated). Note that using incremental backups is not a viable option here, because we lose the benefits of compaction (as discussed in my last comment of CASSANDRA-10960).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org