Well, I don't like clunky and I'm java friendly. I'll go for the abstract class.

Thanks for the help.

On Tue, Mar 9, 2010 at 7:33 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
> On Tue, Mar 9, 2010 at 7:30 AM, Matteo Caprari <matteo.capr...@gmail.com> 
> wrote:
>> On Tue, Mar 9, 2010 at 1:23 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
>>> That's true.  So you'd want to use a custom comparator where first 64
>>> bits is the Long and the rest is the userid, for instance.
>>>
>>> (Long + something else is common enough that we might want to add it
>>> to the defaults...)
>>
>> What about using a SuperColumn for each like-count and then the list
>> of users that hit that level?
>
> That would also work, it's just a little clunky pulling things out of
> a nested structure when really you want a flat list.  But if you are
> allergic to Java that is the way to go so you don't have to write a
> custom AbstractType subclass. :)
>
> -Jonathan
>



-- 
:Matteo Caprari
matteo.capr...@gmail.com

Reply via email to