cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8606) sstablesplit does not remove original sstable
Date Tue, 31 Mar 2015 13:55:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388550#comment-14388550
] 

Branimir Lambov commented on CASSANDRA-8606:
--------------------------------------------

Patch uploaded [here|https://github.com/apache/cassandra/compare/trunk...blambov:8606-sstablesplit-2.1].
- Both sstablesplit and sstableupgrade are changed to call markObsolete() and selfRef().release()
as in sstablescrub after processing a table succeeds.
- An option to keep originals is added to sstableupgrade; sstablesplit does snapshotting and
should not need that.
- Unused verbose option is removed from sstablesplit.

> sstablesplit does not remove original sstable
> ---------------------------------------------
>
>                 Key: CASSANDRA-8606
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8606
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Branimir Lambov
>             Fix For: 2.1.4
>
>
> sstablesplit leaves the original file on disk, it should not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message