On Sun, Apr 25, 2010 at 5:43 PM, Jonathan Ellis wrote:
> On Sun, Apr 25, 2010 at 5:40 PM, Tatu Saloranta wrote:
>>> Now with TimeUUIDType, if two UUID have the same timestamps, they are
>>> ordered
>>> by bytes order.
>>
>> Naively for the whole UUID? That would not be good, given that
>> timest
On Sun, Apr 25, 2010 at 5:40 PM, Tatu Saloranta wrote:
>> Now with TimeUUIDType, if two UUID have the same timestamps, they are ordered
>> by bytes order.
>
> Naively for the whole UUID? That would not be good, given that
> timestamp within UUID is not stored in expected lexical order, but
> with
On Sat, Apr 24, 2010 at 2:08 AM, Sylvain Lebresne wrote:
> On Sat, Apr 24, 2010 at 12:53 AM, Jesse McConnell
> wrote:
>> try LexicalUUIDType, that will distinguish the secs correctly
>>
>> imo based on the existing impl (last I checked at least) TimeUUIDType
>> was equivalent to LongType
>
> It u
On Sat, Apr 24, 2010 at 12:53 AM, Jesse McConnell
wrote:
> try LexicalUUIDType, that will distinguish the secs correctly
>
> imo based on the existing impl (last I checked at least) TimeUUIDType
> was equivalent to LongType
It uses to be true that the TimeUUIDType comparator was only comparing th
try LexicalUUIDType, that will distinguish the secs correctly
imo based on the existing impl (last I checked at least) TimeUUIDType
was equivalent to LongType
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Fri, Apr 23, 2010 at 17:51, Lucas Di Pentima wrote:
> Hello,
>
> I'm us
Hello,
I'm using Cassandra 0.6.1 with ruby library
I want to log events on a CF like this:
Events = { // CF CompareWith: TimeUUIDType
SomeEventID : { // Row
uuid_from_unix_timestamp : event_data,
...
}
}
I receive event data with a UNIX timestamp (nr of seconds passed si
