News for hackers. Stuff that matters.
Re:Distributed SQL vs. NewSQL by rdtsc on Tuesday January 28, 2020 @02:29PM (#22173159)
From your link:

> 2019-09-05: YugaByte’s blog post states YugaByte DB “passes Jepsen tests”. We feel obligated to state that YugaByte DB’s Jepsen test suite does not pass, though it may in the future. Race conditions in YugaByte DB’s schema system can cause correctness errors. For example, inserting rows into a freshly-created table with DEFAULT values may result in the values for those columns initialized to NULL instead. We can also now confirm that this issue affects all default values, not just DEFAULT NOW(). It also appears that DDL race conditions might, under certain conditions, render tables completely unusable.

Yikes. I understand the need for marketing and making their product look good but it's going a bit too far saying they pass the tests when they didn't. I can easily see potential customers pausing when encountering that kind of attitude from YugabyteDB's developers. "What else are they dishonest about..." kind of idea.

Re:Distributed SQL vs. NewSQL by willvarfar on Tuesday January 28, 2020 @03:02PM (#22173485)
I don’t know the case at yugabyte but, in general, the outright lies by sales has nothing to do with the integrity of the developers.
Re:Distributed SQL vs. NewSQL by gauravahuja on Tuesday January 28, 2020 @04:48PM (#22174419)
Developers are responsible for fair benchmarks.