incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian O'Neill <b...@alumni.brown.edu>
Subject Re: CQL/CLI Experiments w/ 1.2
Date Mon, 10 Dec 2012 18:33:28 GMT

Thanks for the explanation(s).

I'm going to give a "Create your first java app for Cassandra" webinar on
Wednesday, and I was trying to embrace schema creation in CQL, but didn't
want to have to use CompositeType's right off the bat.  (I'll go with
compact storage)

I think I can explain away the empty row/column, but we should probably
publicize that.  I can see that question coming up on every client/api
user list. (hector, astyanax, etc.)

-brian


---
Brian O'Neill
Lead Architect, Software Development
Health Market Science
The Science of Better Results
2700 Horizon Drive € King of Prussia, PA € 19406
M: 215.588.6024 € @boneill42 <http://www.twitter.com/boneill42>  €
healthmarketscience.com

This information transmitted in this email message is for the intended
recipient only and may contain confidential and/or privileged material. If
you received this email in error and are not the intended recipient, or
the person responsible to deliver it to the intended recipient, please
contact the sender at the email above and delete this email and any
attachments and destroy any copies thereof. Any review, retransmission,
dissemination, copying or other use of, or taking any action in reliance
upon, this information by persons or entities other than the intended
recipient is strictly prohibited.
 






On 12/10/12 3:16 AM, "Sylvain Lebresne" <sylvain@datastax.com> wrote:

>There is some more details in
>http://www.datastax.com/dev/blog/thrift-to-cql3 but to answer your
>questions:
>
>
>> Question 1:
>> What is the empty column/value?
>
>
>The technical reasons are here:
>https://issues.apache.org/jira/browse/CASSANDRA-4361. But basically, it's
>a
>CQL3 implementation detail.
>
>Question 2:
>> It also appears as though the column names are CompositeType even
>> though there is only one component:
>
>
>Yes, it is the case, and the reason is that this is required to accept
>collections (even if you don't use collection initially, not using a
>composite means you wouldn't be able to add some later). If you explicitly
>don't want a compositeType underneath, you'll need to use the 'WITH
>COMPACT
>STORAGE' option (in which case you will not be able to use collections
>obviously).
>
>--
>Sylvain



Mime
View raw message