Perhaps an inverted index would work.
supercolumn=5 subcolumn=1036
supercolumn=3 subcolumn=13838
I only used a super column family so that you could have multiple subcolumns
for the same supercolumn.
Peter
2010/3/22 Juan Manuel García del Moral
> Hello
>
> I have this:
>
> get SocialAds.Anoni
natural order is for column names, not values
2010/3/22 Juan Manuel García del Moral :
> I understand, but there isn't a way to define a data schema, and get it
> sorted in the insertion,so then the natural order would match what I need to
> query?
>
>
>
> 2010/3/22 Jonathan Ellis
>>
>> You have
I understand, but there isn't a way to define a data schema, and get it
sorted in the insertion,so then the natural order would match what I need to
query?
2010/3/22 Jonathan Ellis
> You have to fetch the columns and sort client-side, for now.
>
> 2010/3/22 Juan Manuel García del Moral :
> > H
You have to fetch the columns and sort client-side, for now.
2010/3/22 Juan Manuel García del Moral :
> Hello
>
> I have this:
>
> get SocialAds.Anonimos['3539792'];
> => (super_column=Tag,
> (column=1036, value=5, timestamp=1001181414)
> (column=116, value=2, timestamp=1001181414)
>
Hello
I have this:
get SocialAds.Anonimos['3539792'];
=> (super_column=Tag,
(column=1036, value=5, timestamp=1001181414)
(column=116, value=2, timestamp=1001181414)
(column=121988, value=2, timestamp=1001181413)
(column=13838, value=3, timestamp=1001181416)
(column=14105,
