[
https://issues.apache.org/jira/browse/CASSANDRA-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462557#comment-13462557
]
Piotr Kołaczkowski edited comment on CASSANDRA-4049 at 9/25/12 7:33 PM:
------------------------------------------------------------------------
Next version of the patch:
- addCustomComponents marked as public API
- simplified discoverComponentsFor loop
- fileLocking removed from SSTable
- added detection for concurrent access or lightweight file locking (just
replace lockOrFail calls with lock if you want locking back)
was (Author: pkolaczk):
Next version of the patch:
- addCustomComponents marked as public API
- simplified discoverComponentsFor loop
- fileLocking removed from SSTable
- added detection for concurrent access or lightweight file locking (just
replace lockOrFail calls with lock)
> 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.6
>
> Attachments: pluggable_custom_components-1.1.5-2.patch,
> pluggable_custom_components-1.1.5.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
