Hi,
I am experiencing a strange issue when using TimeUUID as columnkeys.
I am storing a number of events with timeUUId as key in a row. Later I try to
query for a slice of that row with a given lower bound timeUUID and
upperBoundTimeUUID (constructed as described in the wiki)
If I inserted the e
Yes, I tried that but then the date does not sort correctly.
--
John Alessi
SocketLabs, Inc.
484-418-1282
On Mar 19, 2010, at 12:12 PM, Jesse McConnell wrote:
> alternately try using LexicalUUIDType, that seems to work
>
> jesse
>
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
>
>
> O
alternately try using LexicalUUIDType, that seems to work
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Fri, Mar 19, 2010 at 11:00, Sylvain Lebresne wrote:
> As said, I agree with that.
> I've thus created a jira issue
> (https://issues.apache.org/jira/browse/CASSANDRA-907).
> The dis
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
wrote:
> imo it is a terrible bug..
>
> the usage of a TimeUUIDType implies that your actually ca
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.mcc
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
But they are different names. In 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
mailto:j...@socketla
On Thu, Mar 18, 2010 at 6:12 PM, John Alessi wrote:
> 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 differen
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.
*
Some of my config:
*
0.01
