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 the possibility to separate the writes
asynchronously
and overload them where we on specific pojos want to write vertices or "CQL3
Composite Key tables"
/je
On Jun 13, 2014, at 7:04 PM, graham sanderson <gra...@vast.com> wrote:
> 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 Burton <bur...@spinn3r.com> wrote:
>
>> 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 means all my data is somewhat opaque to
>> cqlsh.
>>
>> What are my options here? What are you guys doing to work around this
>> problem?
>>
>> --
>>
>> Founder/CEO Spinn3r.com
>> Location: San Francisco, CA
>> Skype: burtonator
>> blog: http://burtonator.wordpress.com
>> … or check out my Google+ profile
>>
>> War is peace. Freedom is slavery. Ignorance is strength. Corporations are
>> people.
>>
>
