On Wed, Jan 19, 2011 at 3:00 PM, Geoff Hendrey <[email protected]> wrote: > I investigated hbasene. The source download relies on ".mapred" api, not > ".mapreduce". It's maven pom doesn't build without a lot of hacking and > fixing unresolved dependencies, and even when I was able to build the > source, I am still out of luck because of the mapred vs mapreduce issue. >
The latter is usually a minor issue (I haven't tried it; I'm just speaking from experience converting MR jobs to use APIs from new package). Are you finding it otherwise Geoff? > Is my only recourse to make a custom build of 0.89 which mixes source > from the 0.26 release of HBase in with the 0.89 release? I would have > thought IndexOutputFormat was an important feature to move forward in > the trunk. > Why do you have to touch HBase at all Geoff? Can you not just make a mapreduce job of adjusted IndexOutputFormat bundling lucene and have it run against HBase APIs? Regards it being an important feature for core HBase, for sure its a nice-to-have, but we've been trying to jettison all but core from HBase and have add-ons live elsewhere. We found that carrying along all contribs and additions with their different rates of development (and with flux in developer interest in keeping up the add-on) proved a drag on core development. St.Ack
