On Fri, Mar 12, 2010 at 7:46 PM, Peter Chang wrote:
> Yes, I can update that one entry. But what if that subcolumn key is used
> across many different places?
>
> ['Jones-Bob']['connections']
> ['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c1']
> ['Crabtree-Sam']['connections']
> ['Hacker-Aly
Yes, I can update that one entry. But what if that subcolumn key is used
across many different places?
['Jones-Bob']['connections']
['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c1']
['Crabtree-Sam']['connections']
['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c1']
['Rice-Brown']['connecti
On Fri, Mar 12, 2010 at 7:21 PM, Peter Chang wrote:
> My original post is probably confusing. I was originally talking about
> columns and I don't see what the solution is.
Sorry, I misunderstood.
* "So I was thinking I set the subcolumn compareWith to UTF8Type or
> BytesType and construct a k
To be more explicit:
['500c9280-2cdd-11df-869b-005056c1'] ['connections']
['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c1']
['500c9280-2cdd-11df-869b-005056c1'] ['connections']
['Jones-Jim-1a6dd756b0-2ca1-11df-b937-005056c1']
But Alyssa gets married and changes her name to Zambon
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 + use
On Fri, Mar 12, 2010 at 7:07 PM, Peter Chang 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
But wouldn't name + UUID be considered volatile? That was the crux of my
questions.
On Fri, Mar 12, 2010 at 1:07 PM, Brandon Williams wrote:
> On Thu, Mar 11, 2010 at 12:54 AM, Peter Chang wrote:
>
>> I'm wondering about good strategies for picking keys that I want to be
>> lexically sorted in
On Thu, Mar 11, 2010 at 12:54 AM, Peter Chang wrote:
> I'm wondering about good strategies for picking keys that I want to be
> lexically sorted in a super column family. For example, my data looks like
> this:
>
> [user1_uuid][connections][some_key_for_user2] = ""
> [user1_uuid][connections][som
