Have been running 0.19.1 candidate 1 since last week in all our envs and it works really well. Even tho candidate 2 is a tiny bit different, I still +1
J-D On Sat, Mar 14, 2009 at 12:32 PM, stack <[email protected]> wrote: > I've posted a new release candidate here: > > http://people.apache.org/~stack/hbase-0.19.1-candidate-2/ > > Should we release this candidate as hbase 0.19.1? > > Please take it for a test spin if you have a chance. Vote closes Wednesday, > the 18th of March. > > Here is the list of issues addressed: http://tinyurl.com/c3em9m > > Thanks, > St.Ack > > > On Fri, Mar 13, 2009 at 11:17 PM, stack <[email protected]> wrote: > >> I agree that our not working with Cascading is sufficient cause to sink the >> release. >> >> Going back over commit logs, >> https://issues.apache.org/jira/browse/HBASE-1240 was incompletely >> applied. The compareTo went in but the earlier addition of the RowResult >> implements Comparable failed to apply . >> >> My fault for not noticing the misapplication. Let me put up a new >> candidate soon. >> >> Thanks Erik, >> St.Ack >> >> >> >> On Fri, Mar 13, 2009 at 9:51 AM, Erik Holstad <[email protected]>wrote: >> >>> -1 on rc 19.1. To get Cascading and HBase working properly with each other >>> we need RowResult to be comparable. >>> This is very important for all those people that want to be able to write >>> MR >>> jobs for HBase using Cascading, because >>> it is not going to work without it. A patch was submitted for this issue >>> but didn't make it into the release candidate. >>> >>> Regards Erik >>> >> >> >
