You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2016/05/19 00:38:13 UTC

[jira] [Commented] (CASSANDRA-11191) Support more flexible offline access to SSTable

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

Yuki Morishita commented on CASSANDRA-11191:
--------------------------------------------

My initial approach will be to create SSTable reader/writer factory that holds {{Directories}}, {{CFMetaData}}(schema), and SSTable configurations. This is basically take some SSTable related methods and params from {{ColumnFamilyStore}} and move them to own class. This way, {{ColumnFamilyStore}} and future SSTable tools can both use this class, and tools do not need to access unnecessary things.

> Support more flexible offline access to SSTable
> -----------------------------------------------
>
>                 Key: CASSANDRA-11191
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11191
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>
> Right now, using SSTableReader/SSTableWriter alone needs certain set ups like {{Config.setClientMode(true)}} or loading schema outside. Even doing so, various options to read/write SSTable offline is fixed and not programatically modifiable.
> We should decouple most of {{org.apache.cassandra.io.sstable}} from other parts of cassandra so that we can easily reuse them in offilne tools.



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