Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jesse.mcconnell@gmail.com
 designates 209.85.211.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Oaw/8hhMuMYIL/G159nIgUknWUISn2JIyHJifcPes2gzXFJuhaqv/iO0BPpMkBzKci
         DWPVEY9aauqwZgh2yxMicHAzdPVpPBu4+2OKk13vHZRO6b+VPWuEcb2SqUPImcYKLeGw
         7lj/DufvCELGFmWnlbb4/MPyFuVUpU/VgP4EA=
MIME-Version: 1.0
In-Reply-To: <ac68ab851003190900lff1e50bg1c5469b18dac95df@mail.gmail.com>
References: <24276CBD-086F-445A-9DD5-E8B131CE7FE3@socketlabs.com>
	 <cdc5ad201003181617t34c58f58ob931d78d5a86f334@mail.gmail.com>
	 <749BC322-7E4C-4D29-B9B6-87C6D2769BC6@socketlabs.com>
	 <ac68ab851003190253n3ce3141i66b38787c2fb62@mail.gmail.com>
	 <a43524d01003190830l79e773d4qc3dd076f91dae1f6@mail.gmail.com>
	 <ac68ab851003190900lff1e50bg1c5469b18dac95df@mail.gmail.com>
Date: Fri, 19 Mar 2010 11:12:40 -0500
Message-ID: <a43524d01003190912n26b8d5b1q3fd96bfe60feb794@mail.gmail.com>
Subject: Re: Issue with TimeUUID
From: Jesse McConnell <jesse.mcconnell@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

alternately try using LexicalUUIDType, that seems to work

jesse

--
jesse mcconnell
jesse.mcconnell@gmail.com


On Fri, Mar 19, 2010 at 11:00, Sylvain Lebresne <sylvain@yakaz.com> wrote:
> As said, I agree with that.
> I've thus created a jira issue
> (https://issues.apache.org/jira/browse/CASSANDRA-907).
> The discussion could continue there.
>
> On Fri, Mar 19, 2010 at 4:30 PM, Jesse McConnell
> <jesse.mcconnell@gmail.com> wrote:
>> imo it is a terrible bug..
>>
>> the usage of a TimeUUIDType implies that your actually caring about
>> the unique bits outside of a timestamp...
>>
>> currently it's nothing more then LongType ColumnFamily backed by
>> System.currentTimeInMillis() as a source for name columns.
>>
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@gmail.com
>>
>>
>>
>> On Fri, Mar 19, 2010 at 04:53, Sylvain Lebresne <sylvain@yakaz.com> wrot=
e:
>>> Just looked at the code and it indeed just compare the
>>> timestamps. I also find it weird and I would be for changing it,
>>> but maybe there was a good reason to do it the way it is (even
>>> if I don't see one right now). I'll let people give their opinion on
>>> that.
>>>
>>> In the meantime, if you need a quick fix for testing, I join you
>>> a two line patch that should fix it.
>>>
>>> --
>>> Sylvain
>>>
>>> On Fri, Mar 19, 2010 at 1:25 AM, John Alessi <john@socketlabs.com> wrot=
e:
>>>> But they are different names. =C2=A0In my example they are:
>>>> 1077e700-c7f2-11de-86d5-f5bcc793a028
>>>> 1077e700-c7f2-11de-982e-6fad363d5f29
>>>> But Cassandra sees them as the same.
>>>> --
>>>> John
>>>>
>>>>
>>>>
>>>> On Mar 18, 2010, at 7:17 PM, Brandon Williams wrote:
>>>>
>>>> On Thu, Mar 18, 2010 at 6:12 PM, John Alessi <john@socketlabs.com> wro=
te:
>>>>>
>>>>> I am having an issue where Cassandra doesn't seem to be able to
>>>>> distinguish between 2 different UUIDs if based on the same exact time=
, and
>>>>> sorting by TimeUUID.
>>>>
>>>> *snip*
>>>>>
>>>>> Cassandra doesn't seem to be able to distinguish between 2 different =
UUIDs
>>>>> if based on the same exact time, and sorting by TimeUUID.
>>>>>
>>>>> What am I missing???
>>>>
>>>> Column names must be distinct. =C2=A0If you insert two columns with th=
e same
>>>> name, one overwrites the other.
>>>> -Brandon
>>>>
>>>>
>>>
>>
>