ect. But that will not solve issue of data colocation(data locality) ?
>
>
>
> From: Sasha Dolgy [mailto:sdo...@gmail.com]
> Sent: Thursday, June 16, 2011 8:47 PM
> To: user@cassandra.apache.org
> Subject: Re: Querying superColumn
>
>
>
> Have 1 ro
Correct. But that will not solve issue of data colocation(data locality) ?
From: Sasha Dolgy [mailto:sdo...@gmail.com]
Sent: Thursday, June 16, 2011 8:47 PM
To: user@cassandra.apache.org
Subject: Re: Querying superColumn
Have 1 row with employee info for country/office/division, each column an
Have 1 row with employee info for country/office/division, each column an
employee id and json info about the employee or a reference.to.another row
id for that employee data
No more supercolumn.
On Jun 16, 2011 1:56 PM, "Vivek Mishra" wrote:
> I have a question about querying super column
>
Well, you are looking for the secondary index.
But for now,AFAIK, the supercolumn can not use secondary index .
On 16/06/2011 13:55, Vivek Mishra wrote:
Now for rowKey 'DEPT1' I have inserted multiple super column like:
*Employee1{*
*Name: Vivek*
*country: India*
*}*
**
*Employee2{*
*Nam
