On Tue, Jul 22, 2014 at 1:26 AM, Robert Coli <rc...@eventbrite.com> wrote: > I'm pretty sure reversed comparator timestamps are a common type of schema, > given that there are blog posts recommending their use, so I struggle to > understand how this was not detected by unit tests.
As Karl has suggested, client driver maintainers have opted to workaround the issue. At gocql, when we ran into this issue, we began a discussion thread to see if this was likely to be a client side or a server side bug. Because we didn't get a response from the discussion, we thought that the most pragmatic thing to do was to implement a workaround in the client. Potentially other driver maintainers have taken a similar course of action. As for the unit tests, I think this issue was only reproducible when upgrading a schema to 2.0.x - are you suggesting that there was/is test coverage for this scenario in the server?
