Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com
 designates 209.85.220.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEd91vBR11PPLV_1+C2BnVXPdkp9A2mOUgXNy1=YyjBNYTTHuw@mail.gmail.com>
References: 
 <CAEd91vBR11PPLV_1+C2BnVXPdkp9A2mOUgXNy1=YyjBNYTTHuw@mail.gmail.com>
Date: Tue, 23 Jul 2013 11:08:25 +0200
Message-ID: 
 <CAKkz8Q0-V4OUVuu-djcWd1s9WFB0UPappqTHtr4GQaGJ8=M2NQ@mail.gmail.com>
Subject: Re: OPP seems completely unsupported in Cassandra 1.2.5
From: Sylvain Lebresne <sylvain@datastax.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=047d7b111d0dac651c04e22a22f9

--047d7b111d0dac651c04e22a22f9
Content-Type: text/plain; charset=ISO-8859-1

> - I know that OPP is deprecated. Is it that OPP completely unsupported? Is
> it stated in upgrade instructions or some where? Did we miss it?
>

Basically yes, OPP is not going to work in 1.2 because of the System
tables. I don't think you'll find any upgrade instructions anywhere because
to be honest, I don't think anyone realized that these new system tables
would break OPP because I think everyone had forgotten than OPP was
existing (rather, when we talk of OPP, we generally imply
ByteOrderedPartitioner).  It's been deprecated for a long time.


> - I could not find any related discussion or jira records about similar
> issue.
>

I'd suggest opening a JIRA. It's too late to change the fact that OPP is
now unsupported I'm afraid, but we should probably make it official by
removing it from the code and documenting that it's unsupported. And it'll
make a reference if anyone else run into that problem.

As for upgrade options, if you are *sure* that all your row keys are
actually ascii, I think switching to ByteOrderedPartitioner would actually
be okay. Otherwise, note sure there is much other choice that manually
migrating all data to a brand new cluster :(

--
Sylvain

--047d7b111d0dac651c04e22a22f9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>- I know that OPP is d=
eprecated. Is it that OPP completely unsupported? Is it stated in upgrade i=
nstructions or some where? Did we miss it?</div>
</div></blockquote><div><br></div><div>Basically yes, OPP is not going to w=
ork in 1.2 because of the System tables. I don&#39;t think you&#39;ll find =
any upgrade instructions anywhere because to be honest, I don&#39;t think a=
nyone realized that these new system tables would break OPP because I think=
 everyone had forgotten than OPP was existing (rather, when we talk of OPP,=
 we generally imply ByteOrderedPartitioner). =A0It&#39;s been deprecated fo=
r a long time.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>- I=
 could not find any related discussion or jira records about similar issue.=
</div>
</div></div></blockquote><div><br></div><div>I&#39;d suggest opening a JIRA=
. It&#39;s too late to change the fact that OPP is now unsupported I&#39;m =
afraid, but we should probably make it official by removing it from the cod=
e and documenting that it&#39;s unsupported. And it&#39;ll make a reference=
 if anyone else run into that problem.</div>
<div><br></div><div>As for upgrade options, if you are *sure* that all your=
 row keys are actually ascii, I think switching to ByteOrderedPartitioner w=
ould actually be okay. Otherwise, note sure there is much other choice that=
 manually migrating all data to a brand new cluster :(</div>
<div><br></div><div>--</div><div>Sylvain</div></div></div></div>

--047d7b111d0dac651c04e22a22f9--