Re: timestamp not found

2010-04-16 Thread Lee Parker
In an attempt to continue trouble shooting these errors, I took the text from one and converted it from hex to ascii. Here is the original error: Required field 'timestamp' was not found in serialized data! Struct: Column(name:61 75 74 68 6F 72 5F 69 63 6F 6E, value:68 74 74 70 3A 2F 2F 61 31 2E 7

Re: timestamp not found

2010-04-15 Thread Lee Parker
I have done more error checking and I am relatively certain that I am sending a valid timestamp to the thrift library. I was testing a switch to the Framed Transport instead of Buffered Transport and I am getting fewer errors, but now the cassandra server dies when this happens. It is starting to

Re: timestamp not found

2010-04-15 Thread Lee Parker
I'm actually using PHP. I do have several php processes running, but each one should have it's own Thrift connection. Lee Parker l...@spredfast.com [image: Spredfast] On Thu, Apr 15, 2010 at 10:53 AM, Jonathan Ellis wrote: > Looks like you are using C++ and not setting the "isset" flag on the

Re: timestamp not found

2010-04-15 Thread Jonathan Ellis
Looks like you are using C++ and not setting the "isset" flag on the timestamp field, so it's getting the default value for a Java long ("0"). If it works "most of the time" then possibly you are using a Thrift connection from multiple threads at the same time, which is not safe. On Thu, Apr 15,

Re: timestamp not found

2010-04-15 Thread Lee Parker
When I am verifying the columns in the mutation map before sending it to cassandra, none of the timestamps are 0. I have had a difficult time recreating the error in a controlled environment so I can see the mutation map that was actually sent. Lee Parker l...@spredfast.com [image: Spredfast] On

Re: timestamp not found

2010-04-15 Thread Mike Malone
Looks like the timestamp, in this case, is 0. Does Cassandra allow zero timestamps? Could be a bug in Cassandra doing an implicit boolean coercion in a conditional where it shouldn't. Mike On Thu, Apr 15, 2010 at 8:39 AM, Lee Parker wrote: > We are currently migrating about 70G of data from mys

timestamp not found

2010-04-15 Thread Lee Parker
We are currently migrating about 70G of data from mysql to cassandra. I am occasionally getting the following error: Required field 'timestamp' was not found in serialized data! Struct: Column(name:74 65 78 74, value:44 61 73 20 6C 69 65 62 20 69 63 68 20 76 6F 6E 20 23 49 6E 61 3A 20 68 74 74 70