> Ditto for additional levels. And if you want each of the intermediate
>> levels, pick a serialization format such as JSON or BSON in addition to the
>> flattened leaf values. Anything in your use case(s) that doesn’t cover?
>> >
>> > -- Jack Krupansky
>>
f values. Anything in your use case(s) that doesn’t cover?
> >
> > -- Jack Krupansky
> >
> > From: Kevin Burton
> > Sent: Friday, June 13, 2014 8:17 PM
> > To: user@cassandra.apache.org
> > Subject: Pattern to store maps of maps...
> >
> > So the ca
gt; a serialization format such as JSON or BSON in addition to the flattened leaf
> values. Anything in your use case(s) that doesn’t cover?
>
> -- Jack Krupansky
>
> From: Kevin Burton
> Sent: Friday, June 13, 2014 8:17 PM
> To: user@cassandra.apache.org
> Subject: Pattern
> *From:* Kevin Burton
> *Sent:* Friday, June 13, 2014 8:17 PM
> *To:* user@cassandra.apache.org
> *Subject:* Pattern to store maps of maps...
>
> So the cassandra map support in CQL is nice but it's got me wanting
> deeper nesting.
>
> For example { "foo&quo
On Fri, Jun 13, 2014 at 7:26 PM, Johan Edstrom wrote:
> We treat this on an Object level in Java as a new table with separate
> Hydration.
> On a Map level we currently utilize an Internal CQL3 map where we replace
> the non scalar values with
> separate tables - we just stick the ID in.
> Same f
13, 2014 8:17 PM
To: user@cassandra.apache.org
Subject: Pattern to store maps of maps...
So the cassandra map support in CQL is nice but it's got me wanting deeper
nesting.
For example { "foo": { "bar": "hello" } }
… but that's not possible with CQL.
O
We treat this on an Object level in Java as a new table with separate Hydration.
On a Map level we currently utilize an Internal CQL3 map where we replace the
non scalar values with
separate tables - we just stick the ID in.
Same for Sets, Arrays and such.
You get more writes but you also have
My personal opinion is that unless you are doing map operations on a CQL3 map
and will always intend to read the whole thing (you don’t have any choice
today), don’t use one at all - use a blob of whatever variety makes sense (e.g.
Json, AVRO, Protobuf etc)
On Jun 13, 2014, at 7:17 PM, Kevin Bu
So the cassandra map support in CQL is nice but it's got me wanting deeper
nesting.
For example { "foo": { "bar": "hello" } }
… but that's not possible with CQL.
Of course… one solution is something like avro, and then store your entire
record as a blob.
I guess that's not TOO bad but that mean
