[jira] [Commented] (CASSANDRA-7773) Allow custom commitlog implementations

["Jason Brown (JIRA)" <ji...@apache.org>]

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

Jason Brown commented on CASSANDRA-7773:
----------------------------------------

Hmm, looking further (into CommitLog.LogRecordAdder), I don't think the current patch will get me what I want. Will dig in a little more to see if there's a reasonably simple way to introduce right abstraction for what I want, else I'll close this ticket.

Note: the v2 patch _does_ allow one to swap out periodic/batch services, but I'm not sure if there's much/any value in that.

> Allow custom commitlog implementations
> --------------------------------------
>
>                 Key: CASSANDRA-7773
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7773
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jason Brown
>            Assignee: Jason Brown
>            Priority: Minor
>              Labels: commit_log
>             Fix For: 2.0.10, 2.1.1
>
>         Attachments: 7773-v1.diff, 7773-v2.diff
>
>
> Allow users to run with custom commitlog implementations. The need is that it is probably too late to add CASSANDRA-6018 to 2.0, and as that will now depend on CASSANDRA-6809, 6018 is probably in the 3.0 timeframe. In the meantime we'd like to experiment with getting encrypted commit logs now (internally). Thus, we need to add in a minor bit of flexibility to allow custom implementations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)