Thanks for the info. Will be ever possible to going throught a secondary
index (since SI is sorted by default)? My use case is to display newest
comments, users, etc. SI from my point of view perfectly fits here.
Thanks :)
Petr Odut.
Dne 2010 10 1 18:26 "Jonathan Ellis" napsal(a):
No, additional
Two questions:
1. So this compaction challenge is a CPU issue or a disk IO issue in your case?
2. In other places people have recommended adjustments from the defaults to
control compaction overhead...did you adjust or experiment with how to control
compaction?
Simon Reavely
On Sep 21, 201
On Sun, Oct 3, 2010 at 11:02 AM, Simon Reavely wrote:
> Two questions:
> 1. So this compaction challenge is a CPU issue or a disk IO issue in your
> case?
> 2. In other places people have recommended adjustments from the defaults to
> control compaction overhead...did you adjust or experiment wi
I got this error on my 0.7.0beta2 install, upgraded from the 0.70 nightly 31/08. If you think it's just bad data let me know. Mu cluster had some tombstone records in there, during the upgrade when I re-added the schema I also reduced the GCGraceSeconds. I have not changed the CF types and the syst
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
"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
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
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
