Re: [VOTE] Release Apache Cassandra 1.2.8

2013-07-27 Thread Carl Yeksigian
+1 On Jul 27, 2013 9:17 PM, "Eric Evans" wrote: > > A regression made its way into 1.2.7 and has since been fixed [2]; I > propose the following artifacts for release as 1.2.8. > > Git SHA1: 0291d696018214000709025c0b806089c2f51e97 > Git HTTP: > http://git-wip-us.apache.org/repos/asf?p=cassandra.

Re: [VOTE] Release Apache Cassandra 1.2.8

2013-07-27 Thread Brandon Williams
+1 On Sat, Jul 27, 2013 at 8:15 PM, Eric Evans wrote: > > A regression made its way into 1.2.7 and has since been fixed [2]; I > propose the following artifacts for release as 1.2.8. > > Git SHA1: 0291d696018214000709025c0b806089c2f51e97 > Git HTTP: > http://git-wip-us.apache.org/repos/asf?p=cas

Re: [VOTE] Release Apache Cassandra 1.2.8

2013-07-27 Thread Jason Brown
+1 On Jul 27, 2013 6:33 PM, "Jonathan Ellis" wrote: > +1 > > On Sat, Jul 27, 2013 at 8:15 PM, Eric Evans wrote: > > > > A regression made its way into 1.2.7 and has since been fixed [2]; I > > propose the following artifacts for release as 1.2.8. > > > > Git SHA1: 0291d696018214000709025c0b80608

Re: [VOTE] Release Apache Cassandra 1.2.8

2013-07-27 Thread Jonathan Ellis
+1 On Sat, Jul 27, 2013 at 8:15 PM, Eric Evans wrote: > > A regression made its way into 1.2.7 and has since been fixed [2]; I > propose the following artifacts for release as 1.2.8. > > Git SHA1: 0291d696018214000709025c0b806089c2f51e97 > Git HTTP: > http://git-wip-us.apache.org/repos/asf?p=cas

[VOTE] Release Apache Cassandra 1.2.8

2013-07-27 Thread Eric Evans
A regression made its way into 1.2.7 and has since been fixed [2]; I propose the following artifacts for release as 1.2.8. Git SHA1: 0291d696018214000709025c0b806089c2f51e97 Git HTTP: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.8-tentative Artifacts: https

Re: Regression in 1.2.7

2013-07-27 Thread Eric Evans
[ Brandon Williams ] > On Sat, Jul 27, 2013 at 2:39 PM, Jonathan Ellis 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 > >

Re: Regression in 1.2.7

2013-07-27 Thread Brandon Williams
On Sat, Jul 27, 2013 at 2:39 PM, Jonathan Ellis 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

Re: Regression in 1.2.7

2013-07-27 Thread Yuki Morishita
+1 On Sat, Jul 27, 2013 at 2:43 PM, Michael Kjellman 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" wrote: >> >> The fix for range tombstone performance [1] introduced a

Re: Regression in 1.2.7

2013-07-27 Thread Michael Kjellman
+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" wrote: > > The fix for range tombstone performance [1] introduced a regression > [2] that breaks slice queries against 1.1-format sstables.

Regression in 1.2.7

2013-07-27 Thread Jonathan Ellis
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 mi