[
https://issues.apache.org/jira/browse/CASSANDRA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747149#action_12747149
]
Jeff Hodges commented on CASSANDRA-197:
---------------------------------------
I find it very odd that we think we're going to "hide" functionality through an
obscure endpoint. And we actually want this to a) be simple to implement a
client side to and b) "look and act" like the rest of the client code because
we're going to use it for the hadoop code.
The combination of this rather odd idea that we can "hide" functionality by
making it harder on someone to use it and having to actually need it and want
it working well for our own uses seem to be counter to one another. Why not
just make it easier on ourselves, and make it clean and simple?
> 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
> Components: Core
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: flexjson.jar, issue197.patchv1, patch197.v2, patch197.v3
>
>
> 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.
