Re: Announcing Riak 1.1 release candidate 2

2012-02-10 Thread David Smith
Hi Mark, We are working on 1160, but the odds are we'll need to provide a patch shortly after the release. It's mostly an annoyance right now (i.e. no data is lost because of it), but an incorrect fix could become something more serious. At the very least, we'll provide a workaround script for 1.1

Re: Announcing Riak 1.1 release candidate 2

2012-02-10 Thread Mark Steele
Just curious, but is bz1160 slated to be fixed for 1.1? Seems kind of serious... On Fri, Feb 10, 2012 at 9:43 AM, Jeremiah Peschka < jeremiah.pesc...@gmail.com> wrote: > Good to know! CorrugatedIron should already let you do that, so we can > keep

Re: Announcing Riak 1.1 release candidate 2

2012-02-10 Thread Jeremiah Peschka
Good to know! CorrugatedIron should already let you do that, so we can keep coasting by on good looks and charm. --- Jeremiah Peschka, MVP Managing Director, Brent Ozar PLF, LLC On Feb 10, 2012, at 12:09 AM, Russell Brown wrote: > > On 10 Feb 2012, at 03:04, Jeremiah Peschka wrote: > >> Are

Re: Announcing Riak 1.1 release candidate 2

2012-02-10 Thread Russell Brown
On 10 Feb 2012, at 03:04, Jeremiah Peschka wrote: > Are there any protocol changes for client developers to be aware of, or are > we safe? Not strictly a protocol change, but It is possible to run a MapReduce job *without* phases now. If your client previously disallowed this it should change

Re: Announcing Riak 1.1 release candidate 2

2012-02-09 Thread Jeremiah Peschka
Are there any protocol changes for client developers to be aware of, or are we safe? --- Jeremiah Peschka Managing Director, Brent Ozar PLF, LLC On Thu, Feb 9, 2012 at 7:01 PM, Jared Morrow wrote: > The next release candidate has been built and uploaded to our Downloads > page listed below. T