Okay. I found an issue already opened for that
https://issues.apache.org/jira/browse/CASSANDRA-5234 and added it my comment as
it's labeled as 'Not a problem'
thanks
--
Cyril SCETBON
On Mar 26, 2013, at 9:24 PM, aaron morton
mailto:aa...@thelastpickle.com>> wrote:
Is there a way to have the c
> Is there a way to have the column family defined the new way in a DC and the
> old way (WITH COMPACT STORAGE) in another DC ?
No.
Try a search of https://issues.apache.org/jira/browse/CASSANDRA to see if there
is an existing ticket for PIG to support CQL 3. If not, raise one describing
your
No one else concerned by the fact that we must define the column families the
old way to access it with Pig ?
Is there a way to have the column family defined the new way in a DC and the
old way (WITH COMPACT STORAGE) in another DC ?
Thanks
--
Cyril SCETBON
Expert bases de données
Humanlog pou
On Mar 20, 2013, at 5:21 AM, aaron morton wrote:
> By design. There may be a plan to change in the future, I'm not aware of one
> though.
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 tables
w
By design. There may be a plan to change in the future, I'm not aware of one
though.
CQL 3 tables created without COMPACT STORAGE store all keys and columns using
Composite Types. They also store some additional columns you may not expect.
If you want to interrop with thrift based API's like
Hi,
I'm testing Pig (0.11) with Cassandra (1.2.2). I've noticed that when the
column family is created without WITH COMPACT STORAGE clause, Pig can't find it
:(
After searching in the code, I've found that the issue comes from the function
recv_describe_keyspace. This function returns a KsDef w
