cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-197) Expose ring map to client for more direct access
Date Fri, 22 May 2009 20:48:47 GMT

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

Jonathan Ellis commented on CASSANDRA-197:
------------------------------------------

Okay, so you're kind of taking a hybrid approach where the "client" is including large parts
of the cassandra server code, and needs the server config file, but doesn't actually get the
benefits of being part of the gossip layer.

I think that's fine as a halfway measure that you can use privately but the "right thing"
is to go the other 10% of the way towards being a member of the cluster instead of hacking
some of the data out via the client API.

> Expose ring map to client for more direct access
> ------------------------------------------------
>
>                 Key: CASSANDRA-197
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-197
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>         Attachments: issue197.patchv1
>
>
> For certain applications, it would be nice if a read is sent to a node that owns the
data locally. This saves an extra network hop. To do that, a client will need to cache the
ring map and use it to figure out the nodes owning a row.

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