[ 
https://issues.apache.org/jira/browse/FLUME-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706148#comment-13706148
 ] 

Hari Shreedharan commented on FLUME-1618:
-----------------------------------------

Hi Roshan,

Some comments:

* Looks like you have merged the hadoop-2 profile with the hbase-95 one. Let's 
do this - create an hbase-95 profile, set a property in the hadoop profiles as 
a suffix to the hbase artifact name (suffix as hadoop-1 for hadoop-1 and 
hadoop-2 for hadoop-2). In the hbase-95 profile, set the version of hbase to be 
${hbase.artifact}-95-${hadoop-suffix}. 

* For now we can leave the Asynchbase tests disabled in the hbase-95 profile.

* The setWriteToWal to setDurability change needs to be done using reflection, 
else builds against hbase-94 will fail.

* There is one additional change in the Syslog Source - that is not relevant to 
this jira. There is also a guava upgrade, let's do that in a different jira (I 
am +1 on upgrading Guava - just in a different jira)

* Why make this change - the Apache staging repo is already in the pom:
{code}
+    <repoid>apache.staging.https</repoid>
+    
<repourl>https://repository.apache.org/service/local/staging/deploy/maven2/</repourl>
+    <reponame>Apache Staging Repository</reponame>
+    <repo.maven.org>http://repo1.maven.org/maven2</repo.maven.org>
+    <publicrepoid>public</publicrepoid>
{code}
                
> Make Flume NG build and tests work with Hadoop 2.0
> --------------------------------------------------
>
>                 Key: FLUME-1618
>                 URL: https://issues.apache.org/jira/browse/FLUME-1618
>             Project: Flume
>          Issue Type: Task
>          Components: Build, Test
>            Reporter: Roshan Naik
>            Assignee: Roshan Naik
>              Labels: bigtop
>         Attachments: FLUME-1618.patch, FLUME-1618.v2.patch, 
> FLUME-1618.v3.patch
>
>
> Add hadoop 2.0 support for Flume NG

--
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

Reply via email to