Here is the ticket: https://issues.apache.org/jira/browse/CASSANDRA-1039
2010/4/29 Roland Hänel <firstname.lastname@example.org>:
> Imagine the following rule: if we are in doubt whether to repair a columnThat sounds like an excellent idea to me. Can you create a ticket for
> with timestamp T (because two values X and Y are present within the cluster,
> both at timestamp T), then we always repair towards X if md5(X)<md5(Y). In
> this case, even after an inconsistency on the first insert, this would be
> cleared by any node that triggers a repair afterwards.
> And then you're done: a Cassandra can create a unique transaction ID by
> inserting a column with the ID this clients wants to grab as key, and some
> random stuff as value, then the clients reads the just inserted column, and
> if the ID and the same random stuff is there - voila, the ID is unique for
> this client.
that at https://issues.apache.org/jira/browse/CASSANDRA ?
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support