Re: Modeling nested collection with C* 2.0

Generally, you should use clustering columns to model nested structures, unless they really are simply list/map structures. But, first, as with all data modeling in Cassandra, start by looking at how you intend to query the data. Do you need to query individual addresses, email addresses,

RE: Modeling nested collection with C* 2.0

I need to query all columns by the userid. For example: Select * from users where userid = 123; frozen UDT don’t exist in Cassandra 2.0 ☹ De : Jack Krupansky [mailto:jack.krupan...@gmail.com] Envoyé : jeudi 28 janvier 2016 16:38 À : user@cassandra.apache.org Objet : Re: Modeling nested

Re: Modeling nested collection with C* 2.0

Hi Ahmed, I think modelling them as a map where you can 'label' your emails or addresses sounds like a good option. More info here: https://docs.datastax.com/en/cql/3.1/cql/cql_using/use_map_t.html Regards Carlos Alonso | Software Engineer | @calonso On 28

Re: Modeling nested collection with C* 2.0

y [mailto:jack.krupan...@gmail.com] > *Envoyé :* jeudi 28 janvier 2016 16:38 > *À :* user@cassandra.apache.org > *Objet :* Re: Modeling nested collection with C* 2.0 > > > > Generally, you should use clustering columns to model nested structures, > unless they really are simp

Re: Modeling nested collection with C* 2.0

Ahmed, Just using text and serializing as Json is the easy way and a common approach. However, this list is for Cassandra commiter discussion, please be so kind as to use the regular user list for data modeling questions or for any future responses to this email thread. Regards, Ryan Svihla