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 Tue, 26 May 2009 04:28:45 GMT

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

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

I don't think there's any question that if we had a patch adding the gossip feature I am positing,
vs this one, that the gossip one is the Right Approach to take.  The only problem is that
that is tricky code. :)

If you think about it that way, then I think it's clear that this patch is fine to use locally
as a kludge to achieve what you want but it's not something we want to support as part of
0.4 and beyond.

> 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