cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4049) Add generic way of adding SSTable components required custom compaction strategy
Date Mon, 18 Jun 2012 18:37:42 GMT

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

Piotr Kołaczkowski commented on CASSANDRA-4049:
-----------------------------------------------

Custom1..Custom5 types would be ok, but we'd like they can at least get meaningful names in
the DSE code and in the data-directory. It can pretty fast bite us, if there are files named
sblocks-custom1.dat, sblocks-custom2.dat, etc - the name doesn't tell anything what is inside.
                
> Add generic way of adding SSTable components required custom compaction strategy
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4049
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Piotr Kołaczkowski
>            Assignee: Piotr Kołaczkowski
>            Priority: Minor
>              Labels: compaction
>             Fix For: 1.1.2
>
>         Attachments: compaction_strategy_cleanup.patch, component_patch.diff
>
>
> CFS compaction strategy coming up in the next DSE release needs to store some important
information in Tombstones.db and RemovedKeys.db files, one per sstable. However, currently
Cassandra issues warnings when these files are found in the data directory. Additionally,
when switched to SizeTieredCompactionStrategy, the files are left in the data directory after
compaction.
> The attached patch adds new components to the Component class so Cassandra knows about
those files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message