Thanks guys,
In the end I don't know what solved it, I had changed too much code to know
for sure and too many other things at the same time. I did however find
tcpdump useful as a debug tool as the error messages don't always seem to
make it back up the stack into php. I could read them in plain
The Clock was dropped in beta2, timestamps are back to Int64.
Ahh, my mistake! Thanks for the correction Aaron.
Chris.
On Mon, Oct 4, 2010 at 12:29 AM, Aaron Morton wrote:
> The Clock was dropped in beta2, timestamps are back to Int64.
>
> As Chris says something is not getting what it expecte
The Clock was dropped in beta2, timestamps are back to Int64. As Chris says something is not getting what it expected. I'd double check you are using the latest generated interface, and check the exception stack to see if it's when the client is sending or receiving the message .If you turn logging
"Bad type in structure" means that some property/parameter is of an invalid
type. e.g. a string instead of an object, an object of the wrong class, etc.
One thing that jumps out at me is this line...
$col->timestamp=time();
I believe that all timestamps must now be defined by an instance of
the
I've just installed the latest version of cassandra (0.7.0 beta 2) and
re-made the relevant thrift libraries.
There doesn't seem to be many php examples around so i'm struggling to
get something basic to work. I had it working under 0.6.0 but had
other issues hence the upgrade.
I've tried to exec
