cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-535) Support remote clients via Java API
Date Wed, 25 Nov 2009 20:14:39 GMT

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

Gary Dusbabek updated CASSANDRA-535:
------------------------------------

    Attachment: 535-v1.diff

Here's a first stab.  I tested using both random and ordered partitioning.  commit log and
data directories still get created, although nothing ever gets put there.



> Support remote clients via Java API
> -----------------------------------
>
>                 Key: CASSANDRA-535
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-535
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: T Jake Luciani
>            Assignee: Gary Dusbabek
>             Fix For: 0.9
>
>         Attachments: 535-v1.diff
>
>
> Cassandra should support Java based clients without requiring the overhead of thrift
serialization.
> To support this, a java client should be able to join the gossip pool but provide no
tokens of its own (so it accepts no writes).
> The way this can be done is add a new startup routine to StorageService called startGossip()
that would only initialize itself enough to get access to gossip.
> I don't think its quite this simple though since cassandra code assumes there is at least
one local token in places.
> Also,  all StorageProxy methods used for thrift service should be made public StorageProxy.getKeyRange()
is not public.

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