Re: Modeling Multi-Valued Fields

2011-03-10 Thread Sasha Dolgy
hm. i use this approach and have secondary indexes configured on the columns if i need to do a specific search for an address. alternately, in the user cf, if you wanted to be very uncool, but optimized for always retrieving the user email addresses, you could have the uuid for the user record an

Re: Modeling Multi-Valued Fields

2011-03-10 Thread aaron morton
or all their email addresses), than it is to optimize to read just one particular field. The overall goal here is to optimize your storage model to support read requests, even if it means duplication and de-normalisation. Hope that helps. Aaron On 10 Mar 2011, at 14:43, Cameron Leach wrote:

Modeling Multi-Valued Fields

2011-03-09 Thread Cameron Leach
Is there a best-practice for modeling multi-valued fields (fields that are repeated or collections of fields)? Our current data model allows for a User to store multiple email addresses: User { Integer id; //row key List emails; Email { String type; //home, work, gmail, hotmail, etc