Ok. Correct me if am wrong.... Sounds like the general idea here is that we go out now with a profile to support hadoop 0.23 in Flume 1.3 .In a subsequent Flume version we would have a hadoop2 profile which picks up the right HBase version from MVN central once HBase publishes a hadoop2 variety also ? -roshan
On Wed, Oct 17, 2012 at 3:40 PM, Roman Shaposhnik (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/FLUME-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478466#comment-13478466] > > Roman Shaposhnik commented on FLUME-1651: > ----------------------------------------- > > Hari, I think the risk should be pretty minimal, but as I said -- I > haven't been lurking on Flume mailing lists enough to know who may be using > this profile > > > in the hadoop-0.23 profile HBase version needs to be at least 0.94.2 > > --------------------------------------------------------------------- > > > > Key: FLUME-1651 > > URL: https://issues.apache.org/jira/browse/FLUME-1651 > > Project: Flume > > Issue Type: Bug > > Components: Sinks+Sources > > Affects Versions: v1.3.0 > > Reporter: Roman Shaposhnik > > Assignee: Roman Shaposhnik > > Priority: Blocker > > Fix For: v1.3.0 > > > > Attachments: FLUME-1651.patch.txt > > > > > > In order to be compatible with Hadoop 2.X the HBase version has to be at > least 0.94.2. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
