You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2010/06/10 16:46:13 UTC
[jira] Commented: (CASSANDRA-1131) Towards A Formalization Of The
Cassandra Daemon
[ https://issues.apache.org/jira/browse/CASSANDRA-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877433#action_12877433 ]
Gary Dusbabek commented on CASSANDRA-1131:
------------------------------------------
Karthick, can you rebase and reattach this patch? Thanks.
> Towards A Formalization Of The Cassandra Daemon
> -----------------------------------------------
>
> Key: CASSANDRA-1131
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1131
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Karthick Sankarachary
> Attachments: CASSANDRA-1131.patch
>
>
> Right now, we've two implementations of the Cassandra daemon, one that's based on Thrift, and the other on Avro, both of which suffer from a lack of reuse. Specifically, even though they both share the same lifecycle and bootstrapping mechanism, they share no logic.
> Here, we propose an abstraction that captures the concept of a Cassandra daemon, which will allow consumers to seamlessly switch the underlying implementation of their Cassandra daemons. In essence, it defines not only a way to activate and deactivate a Cassandra daemon, but also hooks into its lifecycle methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.