[jira] [Updated] (CASSANDRA-16407) Add possibility to copy SSTables in SSTableImporter instead of moving them

["Marcus Eriksson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-16407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-16407:
----------------------------------------
    Status: Changes Suggested  (was: Review In Progress)

first review posted on the PR

> Add possibility to copy SSTables in SSTableImporter instead of moving them
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16407
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16407
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/SSTable
>            Reporter: Stefan Miklosovic
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> SSTableImporter moves data from source to target. Modify the current code in such a way that source files / SSTables might be copied over, not moved. The reason behind this is that if I have a backup, I do not want to lose that backup after I import it. Backup should stay as it was, untouched. Callers might choose what behavior they require, either importing by moving or importing by copying.
> Please keep in mind that SSTableImporter for firstly introduced in 4.0 trunk and this is seen as a bug basically, I was dedicing between a bug and improvement. I still believe that this should happen BEFORE 4.0 gets out.
> https://github.com/apache/cassandra/pull/875/files
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/331/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org