[
https://issues.apache.org/jira/browse/BIGTOP-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Chu updated BIGTOP-616:
-------------------------------
Description:
Currently, TestHadoopSmoke fails because it looks by default in
/usr/lib/hadoop/contrib/streaming for the Hadoop streaming jar. The streaming
jar has moved to /usr/lib/hadoop-mapreduce.
I edited TestHadoopExamples to look for the examples jar in HADOOP_MAPRED_HOME.
Currently, it wants the user to specify HADOOP_HOME, but this is usually
/usr/lib/hadoop, and in the Bigtop packages the examples jar has moved to
/usr/lib/hadoop-mapreduce.
was:Currently, TestHadoopSmoke fails because it looks by default in
/usr/lib/hadoop/contrib/streaming for the Hadoop streaming jar. The streaming
jar has moved to /usr/lib/hadoop-mapreduce. The patch fixes that.
Summary: Fix TestHadoopSmoke and TestHadoopExamples: tests look for
streaming and examples jar in wrong directory (was: Fix TestHadoopSmoke: looks
for streaming jar in wrong directory)
> Fix TestHadoopSmoke and TestHadoopExamples: tests look for streaming and
> examples jar in wrong directory
> --------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-616
> URL: https://issues.apache.org/jira/browse/BIGTOP-616
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.4.0
> Reporter: Stephen Chu
> Assignee: Stephen Chu
> Fix For: 0.4.0
>
> Attachments: BIGTOP-616.patch
>
>
> Currently, TestHadoopSmoke fails because it looks by default in
> /usr/lib/hadoop/contrib/streaming for the Hadoop streaming jar. The streaming
> jar has moved to /usr/lib/hadoop-mapreduce.
> I edited TestHadoopExamples to look for the examples jar in
> HADOOP_MAPRED_HOME. Currently, it wants the user to specify HADOOP_HOME, but
> this is usually /usr/lib/hadoop, and in the Bigtop packages the examples jar
> has moved to /usr/lib/hadoop-mapreduce.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
