@Jacob - See my this question with the subject - *CQL Tables in Cassandra with an Index*
I just send it out.. Sorry for duplicacy.. After I posted it out, I realize I missed the important details.. On Thu, Nov 7, 2013 at 6:52 PM, Jacob Rhoden <jacob.rho...@me.com> wrote: > > > > On 8 Nov 2013, at 12:54 pm, Techy Teck <comptechge...@gmail.com> wrote: > > > > I am using the below table in our use case - > > > > create table testing1 ( > > employee_id text, > > employee_name text, > > value text, > > last_modified_date timeuuid, > > primary key (employee_name,last_modified_date) > > ); > > Before considering secondary keys, what's the reason for this primary key? > > 1. What happens if two employees have the same name? > > 2. Why is last_modified_date in the primary key? > > >
