modified and resubmitted the patch.
>
>
> -Original Message-
> From: Dr. Andrew Perella [mailto:a...@eutechnyx.com]
> Sent: 18 November 2010 21:40
> To: user@cassandra.apache.org
> Subject: RE: casssandra 0.7beta3, pycassa and windows client timestamps
>
> Thanks
November 2010 21:40
To: user@cassandra.apache.org
Subject: RE: casssandra 0.7beta3, pycassa and windows client timestamps
Thanks for the reminder - I will submit the patch :)
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: 18 November 2010 21:37
To: user
Subject: Re
Thanks for the reminder - I will submit the patch :)
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: 18 November 2010 21:37
To: user
Subject: Re: casssandra 0.7beta3, pycassa and windows client timestamps
Interesting!
Did you post your patch to the Thrift
m]
> Sent: 18 November 2010 00:00
> To: user@cassandra.apache.org
> Subject: Re: casssandra 0.7beta3, pycassa and windows client timestamps
>
>
>
> No, there's no client side caching.
>
> Assuming you're using insert(), could you capture both of these:
> - the r
.
Regards,
Andrew
From: Tyler Hobbs [mailto:ty...@riptano.com]
Sent: 18 November 2010 00:00
To: user@cassandra.apache.org
Subject: Re: casssandra 0.7beta3, pycassa and windows client timestamps
No, there's no client side caching.
Assuming you're using insert(), could you capture both of the
o.com]
Sent: 18 November 2010 00:00
To: user@cassandra.apache.org
Subject: Re: casssandra 0.7beta3, pycassa and windows client timestamps
No, there's no client side caching.
Assuming you're using insert(), could you capture both of these:
- the return value of insert()
- the same thing you
> *Sent:* 17 November 2010 23:34
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: casssandra 0.7beta3, pycassa and windows client timestamps
>
>
>
> Well, the write appears to be succeeding, and since you say this works on
> Linux, it sounds like a client side problem.
>
om
32e4f8f8-2df0-8803-ebb6-ac2eaf2e5...@localhost/127.0.0.1<http://127.0.0.1>
DEBUG 22:59:42,937 resolving 1 responses
DEBUG 22:59:42,937 resolve: 0 ms.
DEBUG 22:59:42,937 quorumResponseHandler: 0 ms.
From: Tyler Hobbs [mailto:ty...@riptano.com<mailto:ty...@riptano.com>]
Sent: 17 Nove
e to 32e4f8f8-2df0-8803-ebb6-ac2eaf2e5...@localhost/
> 127.0.0.1
>
> DEBUG 22:59:42,937 Processing response on a callback from
> 32e4f8f8-2df0-8803-ebb6-ac2eaf2e5...@localhost/127.0.0.1
>
> DEBUG 22:59:42,937 resolving 1 responses
>
> DEBUG 22:59:42,937 resolve: 0 ms.
>
&
134c479110b6f0bb5ca6ea', ttl=None),
super_column=None), deletion=None)
I am just running a single node test machine.
I am using it to run multiple keyspaces for other services (from other clients)
if that might be relevant at all.
From: Tyler Hobbs [mailto:ty...@riptano.com<mailto:ty..
;
>
> I am using it to run multiple keyspaces for other services (from other
> clients) if that might be relevant at all.
>
>
>
>
>
> *From:* Tyler Hobbs [mailto:ty...@riptano.com]
> *Sent:* 17 November 2010 22:33
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: ca
ients)
if that might be relevant at all.
From: Tyler Hobbs [mailto:ty...@riptano.com]
Sent: 17 November 2010 22:33
To: user@cassandra.apache.org
Subject: Re: casssandra 0.7beta3, pycassa and windows client timestamps
Can you give me an example of what your writes look like here?
Are you running a m
et the value updated! Other times I can update many times a
> second – it just seems random!
>
>
>
> *From:* Tyler Hobbs [mailto:ty...@riptano.com]
> *Sent:* 17 November 2010 22:28
> *To:* user@cassandra.apache.org
> *Subject:* Re: casssandra 0.7beta3, pycassa and windows
t: Re: casssandra 0.7beta3, pycassa and windows client timestamps
What resolution does time.time() give you in Windows?
- Tyler
On Wed, Nov 17, 2010 at 4:23 PM, Dr. Andrew Perella
mailto:a...@eutechnyx.com>> wrote:
I have encountered a strange problem with values not being written to Cassandra
ver
What resolution does time.time() give you in Windows?
- Tyler
On Wed, Nov 17, 2010 at 4:23 PM, Dr. Andrew Perella wrote:
> I have encountered a strange problem with values not being written to
> Cassandra very often.
>
> It looks like it is a windows client timestamp problem. I cannot detect a
15 matches
Mail list logo
