From user-return-32355-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Mon Mar 4 15:29:55 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 74D399110 for ; Mon, 4 Mar 2013 15:29:55 +0000 (UTC) Received: (qmail 33903 invoked by uid 500); 4 Mar 2013 15:29:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33761 invoked by uid 500); 4 Mar 2013 15:29:52 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 33747 invoked by uid 99); 4 Mar 2013 15:29:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:29:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a58.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:29:47 +0000 Received: from homiemail-a58.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a58.g.dreamhost.com (Postfix) with ESMTP id F2ABD7D805B for ; Mon, 4 Mar 2013 07:29:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=rkzQw9EkU6c5MplIK2yqbl6dPf A=; b=DKScMGj2DAT9eP3lBciv3K5euRgJuIMmrlqxsAr13HZ/Bx0y10fg3PAgwP 3h7fF7ofzSZ9H+/5fq+YlcuqAgsXa4090AE3roXcgySxwqlS1wB7HulGHuDUtTb2 o3fsa/s5w4jlRyfLmlp4ycM6lZI337nXPtd2VUakgTNxQYsGg= Received: from [192.168.168.119] (c-98-234-52-29.hsd1.ca.comcast.net [98.234.52.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a58.g.dreamhost.com (Postfix) with ESMTPSA id 97E997D8058 for ; Mon, 4 Mar 2013 07:29:35 -0800 (PST) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_38F06E89-3726-44A8-A7AC-43539FF719ED" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: no backwards compatibility for thrift in 1.2.2? (we get utter failure) Date: Mon, 4 Mar 2013 07:29:23 -0800 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_38F06E89-3726-44A8-A7AC-43539FF719ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1250 ok, we are talking about all thrift / cli / hector / no CQL tables not = been read after an upgrade.=20 If you can get some repo steps that would be handy. Cheers =20 ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 4/03/2013, at 5:01 AM, "Hiller, Dean" wrote: > For us, this was an issue creating tables in 1.1.4 using thrift, then = upgrading to 1.2.2. We did not use cli to create anything. I will try = the complete test again today and hopefully get more detail(I didn't = know I could not run the same thrift code in 1.2.2 for keyspace = creation/table creation) >=20 > Thanks, > Dean >=20 > From: aaron morton = > > Reply-To: = "user@cassandra.apache.org" = > > Date: Sunday, March 3, 2013 11:09 PM > To: "user@cassandra.apache.org" = > > Subject: Re: no backwards compatibility for thrift in 1.2.2? (we get = utter failure) >=20 > Dean, > Is this an issue with tables created using CQL 3 ? >=20 > OR=85 >=20 > An issue with tables created in 1.1.4 using the CLI not been readable = after an in place upgrade to 1.2.2 ? >=20 > I did a quick test and it worked. >=20 > Cheers >=20 > ----------------- > Aaron Morton > Freelance Cassandra Developer > New Zealand >=20 > @aaronmorton > http://www.thelastpickle.com >=20 > On 3/03/2013, at 8:18 PM, Edward Capriolo = > wrote: >=20 > Your other option is to create tables 'WITH COMPACT STORAGE'. = Basically if you use COMPACT STORAGE and create tables as you did = before. >=20 > https://issues.apache.org/jira/browse/CASSANDRA-2995 >=20 > =46rom an application standpoint, if you can't do sparse, wide rows, = you break compatibility with 90% of Cassandra applications. So that = rules out almost everything; if you can't provide the same data model, = you're creating fragmentation, not pluggability. >=20 > I now call Cassandra compact storage 'c*' storage, and I call CQL3 = storage 'c*++' storage. See debates on c vs C++ to understand why :). >=20 >=20 > On Sun, Mar 3, 2013 at 9:39 PM, Michael Kjellman = > wrote: > Dean, >=20 > I think if you look back through previous mailing list items you'll = find > answers to this already but to summarize: >=20 > Tables created prior to 1.2 will continue to work after upgrade. New > tables created are not exposed by the Thrift API. It is up to client > developers to upgrade the client to pull the required metadata for > serialization and deserialization of the data from the System column > family instead. >=20 > I don't know Netflix's time table for an update to Astyanax but I'm = sure > they are working on it. Alternatively, you can also use the Datastax = java > driver in your QA environment for now. >=20 > If you only need to access existing column families this shouldn't be = an > issue >=20 > On 3/3/13 6:31 PM, "Hiller, Dean" = > wrote: >=20 >> I remember huge discussions on backwards compatibility and we have a = ton >> of code using thrift(as do many people out there). We happen to have = a >> startup bean for development that populates data in cassandra for us. = We >> cleared out our QA completely(no data) and ran = this=8A.it turns out there >> seems to be no backwards compatibility as it utterly fails. >>=20 >> =46rom astyanax point of view, we simply get this (when going back to >> 1.1.4, everything works fine. I can go down the path of finding out >> where backwards compatibility breaks but does this mean essentially >> everyone has to rewrite their applications? OR is there a list of >> breaking changes that we can't do anymore? Has anyone tried the = latest >> astyanax client with 1.2.2 version? >>=20 >> An unexpected error occured caused by exception RuntimeException: >> = com.netflix.astyanax.connectionpool.exceptions.NoAvailableHostsException: >> NoAvailableHostsException: [host=3DNone(0.0.0.0):0, latency=3D0(0), >> attempts=3D0]No hosts to borrow from >>=20 >> Thanks, >> Dean >=20 >=20 > Copy, by Barracuda, helps you store, protect, and share all your = amazing >=20 > things. Start today: www.copy.com. >=20 >=20 --Apple-Mail=_38F06E89-3726-44A8-A7AC-43539FF719ED Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1250 ok, = we are talking about all thrift / cli / hector / no CQL tables not been = read after an upgrade. 

If you can get some repo = steps that would be = handy.

Cheers
 
http://www.thelastpickle.com

On 4/03/2013, at 5:01 AM, "Hiller, Dean" <Dean.Hiller@nrel.gov> = wrote:

For us, this was an issue creating tables in 1.1.4 using = thrift, then upgrading to 1.2.2.  We did not use cli to create = anything.  I will try the complete test again today and hopefully = get more detail(I didn't know I could not run the same thrift code in = 1.2.2 for keyspace creation/table = creation)

Thanks,
Dean

From: aaron morton <aaron@thelastpickle.com<mailto:aaron@thelastpickle.com= >>
Reply-To: "user@cassandra.apache.org<= ;mailto:user@cassandra.apache.org= >" <user@cassandra.apache.org<= ;mailto:user@cassandra.apache.org= >>
Date: Sunday, March 3, 2013 11:09 PM
To: "user@cassandra.apache.org<= ;mailto:user@cassandra.apache.org= >" <user@cassandra.apache.org<= ;mailto:user@cassandra.apache.org= >>
Subject: Re: no backwards compatibility for thrift in = 1.2.2? (we get utter failure)

Dean,
Is this an issue with = tables created using CQL 3 ?

OR=85

An issue with tables = created in 1.1.4 using the CLI not been readable after an in place = upgrade to 1.2.2 ?

I did a quick test and it = worked.

Cheers

-----------------
Aaron = Morton
Freelance Cassandra Developer
New = Zealand

@aaronmorton
http://www.thelastpickle.com
=
On 3/03/2013, at 8:18 PM, Edward Capriolo = <edlinuxguru@gmail.com<mailto:edlinuxguru@gmail.com>> = wrote:

Your other option is to create tables 'WITH COMPACT = STORAGE'. Basically if you use COMPACT STORAGE and create tables as you = did = before.

https://issues.apache.org/jira/browse/CASSANDRA-2995
=46rom an application standpoint, if you can't do sparse, wide rows, = you break compatibility with 90% of Cassandra applications. So that = rules out almost everything; if you can't provide the same data model, = you're creating fragmentation, not pluggability.

I now call = Cassandra compact storage 'c*' storage, and I call CQL3 storage 'c*++' = storage. See debates on c vs C++ to understand why :).


On = Sun, Mar 3, 2013 at 9:39 PM, Michael Kjellman = <mkjellman@barracuda.com<mailto:mkjellman@barracuda.com>> = wrote:
Dean,

I think if you look back through previous mailing = list items you'll find
answers to this already but to = summarize:

Tables created prior to 1.2 will continue to work = after upgrade. New
tables created are not exposed by the Thrift API. = It is up to client
developers to upgrade the client to pull the = required metadata for
serialization and deserialization of the data = from the System column
family instead.

I don't know Netflix's = time table for an update to Astyanax but I'm sure
they are working on = it. Alternatively, you can also  use the Datastax java
driver in = your QA environment for now.

If you only need to access existing = column families this shouldn't be an
issue

On 3/3/13 6:31 PM, = "Hiller, Dean" = <Dean.Hiller@nrel.gov<mailto:Dean.Hiller@nrel.gov>> = wrote:

I remember huge discussions on = backwards compatibility and we have a ton
of code using thrift(as do = many people out there).  We happen to have a
startup bean for = development that populates data in cassandra for us.  We
cleared = out our QA completely(no data) and ran this=8A.it<http://this=8A.it>= turns out there
seems to be no backwards compatibility as it utterly = fails.

=46rom astyanax point of view, we simply get this (when = going back to
1.1.4, everything works fine.  I can go down the = path of finding out
where backwards compatibility breaks but does = this mean essentially
everyone has to rewrite their applications? =  OR is there a list of
breaking changes that we can't do = anymore?  Has anyone tried the latest
astyanax client with 1.2.2 = version?

An unexpected error occured caused by exception = RuntimeException:
com.netflix.astyanax.connectionpool.exceptions.NoAvai= lableHostsException:
NoAvailableHostsException: = [host=3DNone(0.0.0.0):0, latency=3D0(0),
attempts=3D0]No hosts to = borrow from

Thanks,
Dean


Copy, by = Barracuda, helps you store, protect, and share all your = amazing

things. Start today: = www.copy.com<http://www.copy.com/>.


= --Apple-Mail=_38F06E89-3726-44A8-A7AC-43539FF719ED--