> How does approach B work in CQL. Can we read/write a JSON
> easily in CQL? Can we extract a field from a JSON in CQL
> or would that need to be done via the client code?
Via client code. Support for this is much the same as support for JSON
CLOBs in an RDBMS.
Approach A is better if you ar
On Wed, Sep 19, 2012 at 3:32 PM, Brian O'Neill wrote:
> That said, I'm keeping a close watch on:
> https://issues.apache.org/jira/browse/CASSANDRA-3647
>
> But if this is CQL only, I'm not sure how much use it will be for us
> since we're coming in from different clients.
> Anyone know how/if coll
On Wed, Sep 19, 2012 at 2:00 PM, Roshni Rajagopal
wrote:
> Hi,
>
> There was a conversation on this some time earlier, and to continue it
>
> Suppose I want to associate a user to an item, and I want to also store 3
> commonly used attributes without needing to go to an entity item column
> famil
Client code. CQL will only deserialize composites as you mention in A.
On Sep 19, 2012, at 5:01 AM, "Roshni Rajagopal"
mailto:roshni_rajago...@hotmail.com>> wrote:
Hi,
There was a conversation on this some time earlier, and to continue it
Suppose I want to associate a user to an item, and I w
Roshni,
We're going through the same debate right now.
I believe native support for JSON (or collections) is on the docket
for Cassandra.
Here is a discussion we had a few months ago on the topic:
http://comments.gmane.org/gmane.comp.db.cassandra.devel/5233
We presently store JSON, but we're con
