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-005056c00001'] ['Crabtree-Sam']['connections'] ['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c00001'] ['Rice-Brown']['connections'] ['Hacker-Alyssa-1ab54760-2ca8-11df-aabd-005056c00001'] ... I can update every single entry but now I need to keep track of them (which I guess I'm doing anyway). I was wondering if there was a more elegant solution but it seems unlikely based on the given constraints. On Fri, Mar 12, 2010 at 5:26 PM, Brandon Williams <dri...@gmail.com> wrote: > On Fri, Mar 12, 2010 at 7:21 PM, Peter Chang <pete...@gmail.com> 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 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. >> > > When their name changes, you delete the existing column and insert a new > one with the correct name, which will then sort correctly. > > -Brandon >
