https://issues.apache.org/jira/browse/CASSANDRA-3935
On 2/20/12 7:07 PM, "Jonathan Ellis" wrote:
>Hmm, that dates back to early 0.7... I think the intent is to skip
>deleted hints, even if the tombstoned hints haven't expired yet (and
>thus would not be elided by the getCF filter). Sounds lik
Hmm, that dates back to early 0.7... I think the intent is to skip
deleted hints, even if the tombstoned hints haven't expired yet (and
thus would not be elided by the getCF filter). Sounds like that's
breaking pagination. Normally, all hints get delivered at once and
then we compact away the to
Thanks!
On Mon, Feb 20, 2012 at 5:43 PM, Jukka Zitting wrote:
> Hi Cassandra devs,
>
> The following pull request was submitted against
> https://github.com/apache/cassandra. I've configured the Git mirror to
> forward any future pull requests like that directly to dev@cassandra.
>
> BR,
>
> Jukk
Hi Cassandra devs,
The following pull request was submitted against
https://github.com/apache/cassandra. I've configured the Git mirror to
forward any future pull requests like that directly to dev@cassandra.
BR,
Jukka Zitting
-- Forwarded message --
From: Git at Apache
Date: M
I'm testing hinted handoff in 1.1 beta1 and cannot seem to get a hint
delivered. 3 node cluster, RF = 3, writing with CL = ONE. killed a host then
did the write using the CLI on another node. I can see hint waiting using CLI
and I see the log messages at the end of this email. this suggests
I have a github fork of hector that deals with the removed key and row
cache settings in the column family meta data. I needed this because it
helped me build hive 0.8 and c* in the same jvm. But it is useful because
older Hector clients have trouble talking to 1.1 if you try anything meta
data re
I count 3 binding +1's, one other +1 and no -1's. The vote passes.
I'll get the artifacts published.
--
Sylvain
On Fri, Feb 17, 2012 at 5:34 AM, Peter Schuller
wrote:
> +1
>
> --
> / Peter Schuller (@scode, http://worldmodscode.wordpress.com)
