On Fri, Jun 13, 2014 at 7:26 PM, Johan Edstrom <seij...@gmail.com> 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 for Sets, Arrays and such.
>
>
Yeah.. that's one pattern. In this case we're always reading the same
values back out… and I want to stream my reads so having a foreign key
defeats the whole point of denormalization.

Plus… thèse don't really need lookup normally.


-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
Skype: *burtonator*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>
War is peace. Freedom is slavery. Ignorance is strength. Corporations are
people.

Reply via email to