cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-4049) Add generic way of adding SSTable components required custom compaction strategy
Date Wed, 20 Jun 2012 11:56:43 GMT


Piotr Kołaczkowski commented on CASSANDRA-4049:

If Component.Type was not a static enum, we could provide an API to register new component
types. So DSE could invoke that API on startup, register all components required for its custom
compaction strategies, and then C* would know about all the components, and we could use components
with whatever names we like. If you like the idea, I can do it. 
> Add generic way of adding SSTable components required custom compaction strategy
> --------------------------------------------------------------------------------
>                 Key: CASSANDRA-4049
>                 URL:
>             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
> 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:!default.jspa
For more information on JIRA, see:


View raw message