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 cscetbon.ext@orange.com
 designates 193.251.215.92 as permitted sender)
From: <cscetbon.ext@orange.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Wed, 20 Mar 2013 09:59:19 +0100
Subject: Re: recv_describe_keyspace bug in
 org.apache.cassandra.thrift.Cassandra ?
Thread-Topic: recv_describe_keyspace bug in
 org.apache.cassandra.thrift.Cassandra ?
Thread-Index: Ac4lSTTNhjm53C9gS5aitDUMbjK3jA==
Message-ID: 
 <4259_1363769959_51497A67_4259_9377_1_091498D1-5DC8-45C7-B816-248982A0B98D@orange.com>
References: 
 <25520_1363691377_51484771_25520_100_6_24789DD3-567C-4C57-BF84-40E3DD7EB149@orange.com>
 <C9B6DC51-9832-4CEE-994A-52F9CD25C4C5@thelastpickle.com>
In-Reply-To: <C9B6DC51-9832-4CEE-994A-52F9CD25C4C5@thelastpickle.com>
Accept-Language: fr-FR
Content-Language: en-US
acceptlanguage: fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Mar 20, 2013, at 5:21 AM, aaron morton <aaron@thelastpickle.com> wrote:

> By design. There may be a plan to change in the future, I'm not aware of =
one though.=20
bad news. If someone else has more information about that, don't hesitate !
Do you know how hard it would be to change this behaviour ? to not skip tab=
les without compact storage format
>=20
> CQL 3 tables created without COMPACT STORAGE store all keys and columns u=
sing Composite Types. They also store some additional columns you may not e=
xpect.=20
I suppose that if we are aware of that we can take it into account. And tha=
t's the job of the Pig script to take  only the columns it wants
>=20
> If you want to interrop with thrift based API's like PIG it's best to use=
 COMPACT STORAGE.=20
yes, but it means that I must recreate tables in production, and that rows =
will be stored in a single column on disk which may hurt performance. It's =
said in the documentation that this format is an old one that should be avo=
ided. I suppose there are other issues with it that could  be found ??
>=20
> You can always create CF's the old way using the cassandra-cli.=20

Regards
>=20
> Cheers
>=20
> -----------------
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>=20
> @aaronmorton
> http://www.thelastpickle.com
>=20
> On 20/03/2013, at 12:09 AM, cscetbon.ext@orange.com wrote:
>=20
>> Hi,
>>=20
>> I'm testing Pig (0.11) with Cassandra (1.2.2). I've noticed that when th=
e column family is created without WITH COMPACT STORAGE clause, Pig can't f=
ind it :(
>> After searching in the code, I've found that the issue comes from the fu=
nction recv_describe_keyspace. This function returns a KsDef with an empty =
cf_defs array when there is no column family with COMPACT STORAGE clause. I=
 conclude that all column families that must be accessed by Pig must be def=
ined with this storage clause, but I wandering if it is a bug ? I suppose ..
>>=20
>> Thanks.
>> --=20
>> Cyril SCETBON
>>=20
>> ________________________________________________________________________=
_________________________________________________
>>=20
>> Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages=
 electroniques etant susceptibles d'alteration,
>> France Telecom - Orange decline toute responsabilite si ce message a ete=
 altere, deforme ou falsifie. Merci.
>>=20
>> This message and its attachments may contain confidential or privileged =
information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and d=
elete this message and its attachments.
>> As emails may be altered, France Telecom - Orange is not liable for mess=
ages that have been modified, changed or falsified.
>> Thank you.
>>=20
>=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.