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.mcconn...@gmail.com On Fri, Mar 19, 2010 at 04:53, Sylvain Lebresne <sylv...@yakaz.com> wrote: > 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 <j...@socketlabs.com> wrote: >> 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 <j...@socketlabs.com> 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 different UUIDs >>> if based on the same exact time, and sorting by TimeUUID. >>> >>> What am I missing??? >> >> Column names must be distinct. If you insert two columns with the same >> name, one overwrites the other. >> -Brandon >> >> >
