Changing my vote after J-D and I did a bit of digging. HBASE-2986 is a fix for HBASE-1845, the issue that added multi*; i.e. multiget, multidelete, etc. This 0.89 was cut from the branch before hbase-1845 was applied.
+1 St.Ack On Fri, Sep 24, 2010 at 4:21 PM, Stack <st...@duboce.net> wrote: > -1 (Sorry). We need HBASE-2986. Without it client hangs if a split > in the midst of a put. > > Otherwise, I'd already checked it out -- doc looks good, ran under > load on a cluster -- and would have +1'd it only for your calling out > the absence of HBASE-2986 J-D. > > St.Ack > > > On Fri, Sep 24, 2010 at 4:03 PM, Jean-Daniel Cryans <jdcry...@apache.org> > wrote: >> The 0.89.20100830 DR branch was cancelled, here's the new RC off a new >> branch. >> >> As discussed, this release candidate contains a revert of HBASE-2694 >> which means that it is back on the "very" old master. It is also very >> similar to what we run here in production. >> >> Sources and binaries can be found here: >> >> http://people.apache.org/~jdcryans/hbase-0.89.20100924-candidate-1/ >> >> Documentation: >> >> http://people.apache.org/~jdcryans/hbase-0.89.20100924-candidate-1/hbase-0.89.20100924/docs/ >> >> Here's the list of everything I added since moving from 0830: >> >> HBASE-3008 Memstore.updateColumnValue passes wrong flag to heapSizeChange >> HBASE-3035 Bandaid for HBASE-2990 >> HBASE-2643 Figure how to deal with eof splitting logs >> HBASE-2941 port HADOOP-6713 - threading scalability for RPC reads - to >> HBase >> HBASE-3006 Reading compressed HFile blocks causes way too many DFS RPC >> calls >> severly impacting performance >> HBASE-2989 [replication] RSM won't cleanup after locking if 0 peers >> HBASE-2992 [replication] MalformedObjectNameException in ReplicationMetrics >> HBASE-3034 Revert the regions assignment part of HBASE-2694 (and >> pals) for 0.89 >> HBASE-3033 [replication] ReplicationSink.replicateEntries improvements >> HBASE-2997 Performance fixes - profiler driven >> HBASE-2889 Tool to look at HLogs -- parse and tail -f (patch #2 only) >> >> Unfortunately I forgot to add HBASE-2986 like Stack asked (sorry, I >> just figured it while reading the old voting thread). >> >> Should we release this as the next "Development Release"? Please cast >> your vote by Wednesday, September 29th. >> >> Thanks, >> >> The HBase Team >> >
