[
https://issues.apache.org/jira/browse/CASSANDRA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712216#action_12712216
]
Jun Rao commented on CASSANDRA-197:
-----------------------------------
What you said in the paragraph is not completely true. The purpose of RingCache
is exactly to hide the detailed configurations from the client. RingCache picks
up the setting from the server configuration file so it will adjust to things
like partitioner changes (which likely require both server and client restart)
accordingly. The client code doesn't have to change at all. Take a look at
test/org.apache.cassandra.service.TestRingCache.java and see what you think.
Also, the RingCache layer is much thinner compared with the thrift client.
> 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.
