cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthick Sankarachary (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1131) Towards A Formalization Of The Cassandra Daemon
Date Tue, 25 May 2010 23:52:31 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthick Sankarachary updated CASSANDRA-1131:
---------------------------------------------

    Summary: Towards A Formalization Of The Cassandra Daemon  (was: Towards A Formalization
Of The Cassadra Daemon)

> 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
>    Affects Versions: 0.6.1
>            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.


Mime
View raw message