You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by "Hiller, Dean" <De...@nrel.gov> on 2013/02/05 16:46:23 UTC

where is the UTF8Comparator code for cassandra

Our in-memory version has a slight different we just found out about that we want to fix in the case where we are using UTF8 sorting and our column name
Is String.long.String.  With our in-memory, two different longs are sometimes generating the same string causing a clash and overwriting a location where the
Data should not be put as it should be in it's own column since it is different.  I want to get our implementation correct in simulating cassandra but at a quick glance only found the UTF8Type.java

Thanks,
Dean

Re: where is the UTF8Comparator code for cassandra

Posted by "Hiller, Dean" <De...@nrel.gov>.

Thanks, I misread the code Šgot it now.

Thanks,
Dean

On 2/5/13 9:22 AM, "Edward Capriolo" <ed...@gmail.com> wrote:

>The comparator should be defined in the UTF8Type class.
>
>On Tue, Feb 5, 2013 at 10:46 AM, Hiller, Dean <De...@nrel.gov>
>wrote:
>> Our in-memory version has a slight different we just found out about
>>that we want to fix in the case where we are using UTF8 sorting and our
>>column name
>> Is String.long.String.  With our in-memory, two different longs are
>>sometimes generating the same string causing a clash and overwriting a
>>location where the
>> Data should not be put as it should be in it's own column since it is
>>different.  I want to get our implementation correct in simulating
>>cassandra but at a quick glance only found the UTF8Type.java
>>
>> Thanks,
>> Dean
>>

Re: where is the UTF8Comparator code for cassandra

Posted by Edward Capriolo <ed...@gmail.com>.

The comparator should be defined in the UTF8Type class.

On Tue, Feb 5, 2013 at 10:46 AM, Hiller, Dean <De...@nrel.gov> wrote:
> Our in-memory version has a slight different we just found out about that we want to fix in the case where we are using UTF8 sorting and our column name
> Is String.long.String.  With our in-memory, two different longs are sometimes generating the same string causing a clash and overwriting a location where the
> Data should not be put as it should be in it's own column since it is different.  I want to get our implementation correct in simulating cassandra but at a quick glance only found the UTF8Type.java
>
> Thanks,
> Dean
>