[
https://issues.apache.org/jira/browse/CASSANDRA-16407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294436#comment-17294436
]
Marcus Eriksson commented on CASSANDRA-16407:
---------------------------------------------
this broke the jmx compatibility test:
https://app.circleci.com/pipelines/github/krummas/cassandra/637/workflows/dc4f9152-f239-40d4-a162-ebed52d148eb/jobs/4410
> 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
> Fix For: 4.0.x
>
> Time Spent: 1h 20m
> 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 was 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/376/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
