apache.org/cassandra/ArticlesAndPresentations.
Cheers,
Jérôme Verstrynge
Hi,
I am trying to start a CassandraEmbeddedService for JUnit testing, using
the 'standard' YAML configuration I found in Hector (no modification). I
use 0.7.0-beta2 and I systematically get the following error message:
3687 [main] INFO org.apache.cassandra.config.DatabaseDescriptor -
Loadin
Peter, many thanks for all this information.
On 26/10/2010 21:17, Peter Sculler wrote:
It does mention that timestamps are used for conflict resolution but
does not really dwell on the issue, and the remainder elides
timestamps. So perhaps it's easy to miss. I also notice that the
phrasing is su
Peter, thanks for extensive feedback. Much appreciated.
On 26/10/2010 0:47, Peter Schuller wrote:
This doesn't mean that your problem is somehow invalid; but it doesn't
sound like QUOROM consistency (over-writing) writes is the solution.
What is the difference, from your application's perspec
On 22/10/2010 2:27, Nicholas Knight wrote:
On Oct 22, 2010, at 7:41 AM, Jérôme Verstrynge wrote:
Let's imagine that A initiates its column write at: 334450 ms with 'AAA' and
timestamp 334450 ms
Let's imagine that E initiates its column write at: 334451 ms with 'ZZZ&#x
On 21/10/2010 23:40, Peter Schuller wrote:
OK. Thanks for your answer. From an email exchange I had with Jonathan, all
this means that one should re-read its writes with quorum to make sure they
have not been overriden by timestamp-tie conflicts. I suggested to send
feedback to writting node (in
On 21/10/2010 20:03, Peter Schuller wrote:
My question is: is node E notified that it lost the battle against A? If yes
how?
If not, then it means that, although writes are atomic, they would not be
deterministic. Node E would have to verify that its write was successful...
Quorom is not really
On 21/10/2010 4:43, Jonathan Ellis wrote:
On Wed, Oct 20, 2010 at 8:38 PM, Jérôme Verstrynge wrote:
-) Let's imagine node A updates MyColumn with value 'AAA' and timestamp
3567890
-) Let's imagine node E updates MyColumn with value 'EEE' and timestamp
3567890
Hi,
I am a new to Cassandra. I am reading all the documentation I can find
online.
My question is the following:
-) Let's imagine a cluster with 5 nodes ABCDE. We know that quorum = 3.
-) Let's imagine a column called MyColumn.
-) Let's imagine current timestamp = 3567890.
-) Let's imagine no
