You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kaide Mu (JIRA)" <ji...@apache.org> on 2016/03/01 01:00:21 UTC

[jira] [Commented] (CASSANDRA-8928) Add downgradesstables

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

Kaide Mu commented on CASSANDRA-8928:
-------------------------------------

Hello Apache Cassandra community, 

I'm Kaide Mu, currently pursuing BSc of Computer Science at Polytechnic University of Valencia, Spain. I'd like to work in this issue as my project of GSoC 2016.

About this project, I had been looking in a minor detail for SSTable architecture and some of different available SSTable source code, as I see, there's some different implementations of SSTable, therefore as the issue description indicates, I guess we aim to add a downgradesstable functionality to all existing SSTables, e.g downgrade from a 3.X version SSTable to 2.X SSTable or 1.X ones, please correct if my understanding is wrong.

In addition, would you mind providing me any suggestion or references which I should take a look in order to clarify with this issue, I'd very appreciate it.

Thank you so much and best regards,

Kaide Mu

> Add downgradesstables
> ---------------------
>
>                 Key: CASSANDRA-8928
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8928
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jeremy Hanna
>            Priority: Minor
>              Labels: gsoc2016, mentor
>
> As mentioned in other places such as CASSANDRA-8047 and in the wild, sometimes you need to go back.  A downgrade sstables utility would be nice for a lot of reasons and I don't know that supporting going back to the previous major version format would be too much code since we already support reading the previous version.



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