+1 On Sat, Jul 27, 2013 at 2:43 PM, Michael Kjellman <mkjell...@barracuda.com> wrote: > +1 > > This late in the release cycle it might really bite some people upgrading for > all the 1.2.x goodness. > >> On Jul 27, 2013, at 12:40 PM, "Jonathan Ellis" <jbel...@gmail.com> wrote: >> >> The fix for range tombstone performance [1] introduced a regression >> [2] that breaks slice queries against 1.1-format sstables. Running >> upgradesstables is a workaround, but this means that you can't do >> zero-downtime upgrades from 1.1 at CL.ONE. >> >> I think we should withdraw 1.2.7 from the download mirrors and roll >> 1.2.7.1 with the fix. >> >> Thoughts? >> >> [1] https://issues.apache.org/jira/browse/CASSANDRA-5677 >> [2] https://issues.apache.org/jira/browse/CASSANDRA-5814 >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder, http://www.datastax.com >> @spyced
-- Yuki Morishita t:yukim (http://twitter.com/yukim)
