Yes, looks good here now. - Andy
________________________________ From: Jonathan Gray <[email protected]> To: [email protected] Sent: Thursday, September 17, 2009 12:24:31 PM Subject: Re: Trunk destabilized - Commit of HBASE-1822 Shell fixed with HBASE-1848, MR SampleUploader fixed with HBASE-1850. Passing in Hudson. Woohoo Andrew Purtell wrote: > The shell is broken. > > - Andy > > > > > ________________________________ > From: Andrew Purtell <[email protected]> > To: [email protected] > Sent: Wednesday, September 16, 2009 5:12:20 PM > Subject: Re: Trunk destabilized - Commit of HBASE-1822 > > I'll try it out now in a limited psuedo distributed experiment and will let > you know if I find anything. > Nice work! > > - Andy > > > > > ________________________________ > From: Jonathan Gray <[email protected]> > To: HBase Dev List <[email protected]> > Sent: Wednesday, September 16, 2009 5:00:37 PM > Subject: Trunk destabilized - Commit of HBASE-1822 > > Devs (especially Clint and Tim Sell), > > I just committed HBASE-1822 to 0.21 trunk. (25,000 line patch, eek) > > It completely removes the old API and is an attempt at removing all remaining > references to family:qualifier notation. It drops the mapred and rest > packages completely, in favor of the new mapreduce package and stargate. > Things like HStoreKey, RowResult, and BatchUpdate are gone. > > The only remaining calls related to fam:qf notation are > KeyValue.makeColumn(fam,qf) and KeyValue.parseColumn(col) which takes a > byte[] and splits it on the :. If it's just family it returns a single > dimension only with the family in it, no :. This switched a bit as to how it > worked, and it's used heavily in my adapting Thrift, Stargate, and > Transactional/Indexed to work and pass their tests after ripping out old API > calls they were using. > > Those same contrib modules (should we move thrift to contrib?) really need a > reworking of some sort (stargate is probably fine, except some nastiness in > tests), as they are heavily tied to the old API and their new API > compatibility was just a bolt on. > > So this may have destabilized trunk a bit. Please file issues if you run > into problems. > > All unit tests pass. > > JG > > >
