[ 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
> >
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
+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
+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.
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
