As i mentioned on another email the HBase for hadoop2 versions will have a '-hadoop2' suffix in the version to distinguish them the hadoop1 counterparts. See HBase patch https://issues.apache.org/jira/secure/attachment/12549224/hbase-6929_v2.patch
So I do not think flume will build with the Roman's patch once HBase publishes v2 binaries on MVN central. The version string needs to be changed. Since HBase is likely to publish their H2 binaries in the next release, I was thinking we could wait until then before committing to this patch, otherwise it might be a bit premature. -roshan On Wed, Oct 17, 2012 at 1:16 PM, Hari Shreedharan <[email protected] > wrote: > Flume-1650 was committed sometime back. Looks like Mike is going to commit > FLUME-1651(see jira, he just mentioned it there). > > Roman/Roshan - If Hbase makes the artifacts available on mvn central, > would our build be able to pick it up without any more changes? Or do we > need to make further changes? > > > Thanks, > Hari > > -- > Hari Shreedharan > > > On Wednesday, October 17, 2012 at 12:46 PM, Roman Shaposhnik wrote: > > > On Wed, Oct 17, 2012 at 12:39 PM, Roshan Naik > > <[email protected](mailto: > [email protected])> wrote: > > > I have a patch to support hadoop2 here > > > https://issues.apache.org/jira/browse/FLUME-1618 > > > Its blocked on the availability of an HBase version compiled against > > > Hadoop2. It appears the next release of HBase will publish both > hadoop1 & 2 > > > versions. If you want to get this going locally.. > > > - compile HBase with hadoop 2 profile > > > - grab this patch for flume, revise the HBase version to whatever you > > > built and build Flume using the hadoop-2.0 profile. > > > > > > > > > It seems that a certain percentage of your patch has been covered > > by FLUME-1650 and FLUME-1651. I hope those will be made available > > as part of Flume 1.3.0 release. > > > > Thanks, > > Roman. > > > > > > >
