incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Chang <pete...@gmail.com>
Subject Re: Strategies for storing lexically ordered data in supercolumns
Date Sat, 13 Mar 2010 01:24:18 GMT
To be more explicit:

['500c9280-2cdd-11df-869b-005056c00001'] ['connections']
['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c00001']
['500c9280-2cdd-11df-869b-005056c00001'] ['connections']
['Jones-Jim-1a6dd756b0-2ca1-11df-b937-005056c00001']

But Alyssa gets married and changes her name to Zamboni. The next time I
read these subcolumns the user's will not be sorted.




On Fri, Mar 12, 2010 at 5:21 PM, Peter Chang <peter78@gmail.com> wrote:

> My original post is probably confusing. I was originally talking about
> columns and I don't see what the solution is.
>
> * "So I was thinking I set the subcolumn compareWith to UTF8Type or
> BytesType and construct a key [for the subcolumn, not a row key] *
> *
> *
> *[user's lastname + user's firstname + user's uuid]*
> * *
> *This would result in sorted subcolumn and user list."*
> *
> *
> Nevertheless, I still don't see/understand the solution. Let's say the
> person's name changes. The sort is no longer valid. That column value would
> need to be changed in order for the sort to be correct.
>
>
> On Fri, Mar 12, 2010 at 5:10 PM, Brandon Williams <driftx@gmail.com>wrote:
>
>> On Fri, Mar 12, 2010 at 7:07 PM, Peter Chang <peter78@gmail.com> wrote:
>>
>>> But wouldn't name + UUID be considered volatile? That was the crux of my
>>> questions.
>>
>>
>> It would, but the distinction here is that it is now a column, not a row
>> key.
>>
>>  -Brandon
>>
>
>

Mime
View raw message