[jira] Commented: (CASSANDRA-224) Encapsulate SSTable, SequenceFile better

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-224:
------------------------------------------

05
    make static methods of SSTable that take a filename and then use the cache to grab an sstable object, simple non-static methods instead

04
    encapsulate bloom filter

03
    encapsulate index

02
    refactor read-only constructor to SSTable.open

01
    r/m unused code dealing with sstables, sequencefile, etc.

these patches apply on top of the patches for 79.

> Encapsulate SSTable, SequenceFile better
> ----------------------------------------
>
>                 Key: CASSANDRA-224
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-224
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 0001-CASSANDRA-224-r-m-unused-code-dealing-with-sstables-a.txt, 0002-refactor-read-only-constructor-to-SSTable.open.txt, 0003-encapsulate-index.txt, 0004-encapsulate-bloom-filter.txt, 0005-make-static-methods-of-SSTable-that-take-a-filename-an.txt
>
>
> All kinds of code needs to know about the inner workings of SSTable to work.  A major cause is passing around SSTable filenames instead of objects.  Thanks to CASSANDRA-208 I feel like I have a good enough understanding of the code here to refactor more than superficially.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.