Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 7 May 2015 21:36:00 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12762737.1418951086000.41079.1431034560596@Atlassian.JIRA>
In-Reply-To: <JIRA.12762737.1418951086000@Atlassian.JIRA>
References: <JIRA.12762737.1418951086000@Atlassian.JIRA>
 <JIRA.12762737.1418951086795@arcas>
Subject: [jira] [Resolved] (CASSANDRA-8517) Make client-side Token Aware
 Balancing possible with Global Indexes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-8517?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-8517.
---------------------------------------
    Resolution: Not A Problem

Switching CASSANDRA-6477 syntax from GI to MV will make this a non-problem.

> Make client-side Token Aware Balancing possible with Global Indexes
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-8517
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8517
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Micha=C3=ABl Figui=C3=A8re
>             Fix For: 3.x
>
>
> This is a follow up ticket for CASSANDRA-6477, to consider enabling clien=
t-side Token Awareness Balancing with Global Indexes, a it would be a pity =
to loose this efficient optimization when using these new indexes. My origi=
nal comment was:
> {quote}
> Something that hasn't been mentioned so far in this thread is client side=
's Token Aware Balancing. So far when a query relies on a Secondary Index, =
it doesn't have any partition key specified in its where clause which means=
 that the driver will fall back on the underlying balancing policy, which i=
s DC aware round robin by default in the DS Java Driver. That's the appropr=
iate behavior as there's no node that can be better than another as a coord=
inator in this situation.
> With Global Indexes, in order for the Driver to still be able to perform =
Token Aware Balancing, it'll need to be able to figure out which index will=
 be used, which doesn't seems to be always trivial in the above examples, e=
specially if several columns and/or indexes are involved in the WHERE claus=
e. So here we might need to include an extra information about it in the Pr=
epare response message of the Native Protocol, if the indexes to be involve=
d can be figured out at Prepare-time.
> {quote}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)