On Fri, Dec 9, 2016 at 1:35 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > I copied the wrong issue: > > The core issue was this: https://issues.apache. > org/jira/browse/CASSANDRA-6123 >
Well, my previous remark applies equally well to this ticket so let me just copy-paste: "That ticket has nothing to do with LWT. In fact, LWT is the one mechanism in Cassandra where this ticket has not impact whatsoever because the whole point of the mechanism is to ensure timestamps are assigned in a collision free manner." > Which I believe was one of the key "call me maybe" Created issues. > The "call me maybe" blog post was not at exclusively about LWT and its linearizability, so 6123 may have been an issue created following that post, but it's unrelated to LWT and again, don't affect it. > > 6123 references: this https://issues.apache.org/jira/browse/CASSANDRA-8892 > > > Which duplicates: > > https://issues.apache.org/jira/browse/CASSANDRA-6123 > > So it is unclear to me what was resolved. > Again, it's unrelated to LWT but I don't think there is anything unclear here: 6123 is not resolved as indicated by the jira "resolution". Maybe what you found unclear is that CASSANDRA-8892 has the status "resolved", but that's just JIRA ugliness here: marking a ticket "duplicate" imply "resolving" it as far as JIRA is concerned, so when you see "duplicate", you should basically ignore that ticket and only look the ticket it duplicates.
