The original thread I posted this in got hi-jacked with other discussions, so
I’m making a new thread for this.
People have expressed interest in having more information flow to the dev@ list
about major features/decisions, so that those who don’t follow commits@ or JIRA
can still keep up with
In the spirit of the recent thread about discussing large changes on the
Dev ML, I'd like to talk about CASSANDRA-10993, the first step in the
"thread per core" work.
The goal of 10993 is to transform the read and write paths into an
event-driven model powered by event loops. This means that each
I think I outlined the tradeoffs I see between the roll our own vs use a
reactive framework in
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-10528
My view is we should try to utilize the existing before we start writing
our own. And even if we do write our own keep it react
Hi,
I want to differ hintedhandoff mutation and normal write mutation when i
receive a mutation.
and I agree with the opinion of Chris Lohfink.that no way to tell the
difference.but i cannot use created time as Chris suggested.
because I cannot choose a accurate time to differ them.
anyone have id
===
testall: 1 failure
org.apache.cassandra.service.RemoveTest.testBadHostId
CASSANDRA-12487. Flaky test failure for which I've opened a new
issue. This is almost certainly a test problem, as the failure
occurs in a test utility method.
