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, 2010 at 10:39 AM, Lee Parker <l...@socialagency.com> wrote: > 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 3A 2F 2F 77 77 77 2E 79 6F 75 74 75 62 > 65 2E 63 6F 6D 2F 77 61 74 63 68 3F 76 3D 70 75 38 4B 54 77 79 64 56 77 6B > 26 66 65 61 74 75 72 65 3D 72 65 6C 61 74 65 64 20 40 70 6A 80 01 00 01 00, > timestamp:0) > > The loop which is building out the mutation map for the batch_mutate call > is adding a timestamp to each column. I have verified that the time stamp > is there for several calls and I feel like if the logic was bad, i would see > the error more frequently. Does anyone have suggestions as to what may be > causing this? > > Lee Parker > l...@spredfast.com > > [image: Spredfast] >
