Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <954239613.1250606955012.JavaMail.jira@brutus>
Date: Tue, 18 Aug 2009 07:49:15 -0700 (PDT)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-197) Expose ring map to client for
 more direct access
In-Reply-To: <1983416145.1243011886030.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Evans commented on CASSANDRA-197:
--------------------------------------

How is the client going to know the Partitioner, ReplicaPlacementStrategy, and ReplicationFactor? Are non-java clients expected to re-implement the Partitioner and ReplicaPlacementStrategy? 

Unless I'm missing something, a token-to-node map doesn't seem very useful in the general sense without these.

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