cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7773) Allow custom commitlog implementations
Date Thu, 14 Aug 2014 21:32:19 GMT

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

Jason Brown edited comment on CASSANDRA-7773 at 8/14/14 9:31 PM:
-----------------------------------------------------------------

Attached patch allows user to set the fully qualified java class name in commitlog_sync field
in yaml to declare the commitlog service class. CommitLog's constructor will instantiate that
class (vs. period or sync implementations - no change necessary to keep on using those).


was (Author: jasobrown):
Attached patch allows user to set fully qualified java class name in commitlog_sync field
in yaml. CommitLog's constructor will instantiate the class.

> 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
>
>
> 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)

Mime
View raw message