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

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

> It doesn't [fit Jeff's needs] for reasons already discusse

I don't follow.  Over in CASSANDRA-342 I see

[Stu] Good call... the RingCache mentioned on CASSANDRA-197 is exactly what 
this ticket needs.

[Jeff] Yep, that is exactly what I was thinking about. I'll nose myself around 
over there.

I don't see where you explain how this doesn't work.  I'm sure I'm just missing 
something.

> 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

No

> because we're going to use it for the hadoop code.

Yes.  One rule of API design is to make it easy to do the right thing and hard 
to do the wrong one.  99% of clients should not use this API and we do not want 
to encourage them.  Only Hadoop and some very specialized apps will want or 
need it.  Read Eric's comments above; this is not code that any Thrift client 
can just use with or without a "real" Thrift api; it requires embedding 
nontrivial parts of the Cassandra server (hence, the jvm as well, which 
immediately rules out many Thrift consumers).

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

Reply via email to