Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rantav@gmail.com designates
 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=b0j94Txd4xiC8wlTbgxbJw/aKwvfnMWPPdSDb2yZxlGZ/8NhQkI/wGL+sgKObIucuC
         BGiMoeS8CpYUzZ5G1c0E2LGiBLyfw8QJsraLKXaVU/saUfQuE4vohCiywic5qDFUUePV
         slOJpefIL2SlfsHp2PyhZ4+1yKgCOJd2QYiJ8=
MIME-Version: 1.0
From: Ran Tavory <rantav@gmail.com>
Date: Wed, 18 Aug 2010 15:56:48 +0300
Message-ID: <AANLkTimQMAuz-TOJNku4H=RhZ_adSLdd_EJeLMM8QfO7@mail.gmail.com>
Subject: KeyRange.token in 0.7.0
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001485f4504e7109e6048e189a36

--001485f4504e7109e6048e189a36
Content-Type: text/plain; charset=UTF-8

I'm a bit confused WRT KeyRange's tokens in 0.7.0
When making a range query you can either use KeyRange.key or KeyRange.token.
In 0.7.0 key was typed as byte[]. tokens remain strings.
What does this string represent in case of a RP and in case of an OPP? Did
this change in 0.7.0?

AFAIK in 0.6.0 if the partitioner is OPP then the tokens are actual strings
and they might just be actual subset of the keys. When using a RP tokens are
BigIntegers (keys are still strings) and I'm not actually sure if you're
allowed to shoot a range query using tokens...

In 0.7.0 since keys are now bytes, when using an OPP, how do those bytes
translate to strings? I'd assume it'd just be byte[] -> UTF8 conversion,
only that this may result in illegal UTF8 chars when keys are just random
bytes, so I guess not... Perhaps md5 hashing? But then if using an OPP and
keys are actual strings, I want to have the same 0.6.0 functionality in
place, meaning tokens are strings like the keys. I actually tested this
scenario and it looks working, so it seems like the String keys are
translated to UTF8, but what happens when they are invalid UTF8?
Another question is what's the story with RP in 0.7.0? Should range query
even be supported with tokens? If so, then are the tokens expected to be
string of integers? (e.g. "1234567890")

Thanks.

--001485f4504e7109e6048e189a36
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m a bit confused WRT KeyRange&#39;s tokens in 0.7.0<=
div>When making a range query you can either use KeyRange.key or KeyRange.t=
oken. In 0.7.0 key was typed as byte[]. tokens remain strings.</div><div>Wh=
at does this string represent in case of a RP and in case of an OPP? Did th=
is change in 0.7.0?</div>

<div><br></div><div>AFAIK in 0.6.0 if the partitioner is OPP then the token=
s are actual strings and they might just be actual subset of the keys. When=
 using a RP tokens are BigIntegers (keys are still strings) and I&#39;m not=
 actually sure if you&#39;re allowed to shoot a range query using tokens...=
</div>

<div><br></div><div>In 0.7.0 since keys are now bytes, when using an OPP, h=
ow do those bytes translate to strings? I&#39;d assume it&#39;d just be byt=
e[] -&gt; UTF8 conversion, only that this may result in illegal UTF8 chars =
when keys are just random bytes, so I guess not... Perhaps md5 hashing? But=
 then if using an OPP and keys are actual strings, I want to have the same =
0.6.0 functionality in place, meaning tokens are strings like the keys. I a=
ctually tested this scenario and it looks working, so it seems like the Str=
ing keys are translated to UTF8, but what happens when they are invalid UTF=
8?</div>

<div>Another question is what&#39;s the story with RP in 0.7.0? Should rang=
e query even be supported with tokens? If so, then are the tokens expected =
to be string of integers? (e.g. &quot;1234567890&quot;)</div><div><br>
</div>
<div>Thanks.</div></div>

--001485f4504e7109e6048e189a36--