[
https://issues.apache.org/jira/browse/CASSANDRA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713381#action_12713381
]
Eric Evans commented on CASSANDRA-197:
--------------------------------------
"So to me when I say a "client level api" I strictly mean one we expose via
thrift to processes that are not expected to know anything about the Cassandra
internals. As soon as you say "we should expose this to the client, but it will
need to use (non-thrift) org.apache.cassandra classes and the server .xml file"
then we are in violation of this implicit contract."
I agree with this. In fact, I was concerned we doing exactly that (violating
this implicit contract) when we added the new block_for arguments which assume
client-side knowledge of the replication policy.
Personally, I'd hate to see us go any further in this direction.
> 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.
