You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2009/06/17 19:40:07 UTC

[jira] Updated: (CHUKWA-297) Unbundling hadoop jar file

     [ https://issues.apache.org/jira/browse/CHUKWA-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated CHUKWA-297:
-----------------------------

    Priority: Minor  (was: Blocker)

Due to the fix for CHUKWA-302, this is no longer a blocker.  The only refinement is to download hadoop jar file from maven to make the build as finalizing this issue.  However, hadoop jar file is currently not part of maven, hence table this issue aside until hadoop jar is published to maven repository.

> Unbundling hadoop jar file
> --------------------------
>
>                 Key: CHUKWA-297
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-297
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: build and test code
>    Affects Versions: 0.1.2, 0.2.0
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Minor
>
> During the deployment, the most frequently issue is hadoop version mismatch.  When this happens, the hadoop jar files needs to be copied to both CHUKWA_HOME/hadoopjars, and hicc/WEB-INF/lib.  We should be able to work around both issues by using environment controlled class path.  For build time, the HADOOP_JAR variable could be overwritten by default.properties and build.properties to source in hadoop jar file.  If this is this sounds good, then I vote for removing the hadoop-*.jar file from hadoopjars directory in the upcoming release.  This change would reduce the amount of hand tweak on the deployment system.  Suggestion and feedback are welcome.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.