[
https://issues.apache.org/jira/browse/BIGTOP-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909503#comment-13909503
]
jay vyas commented on BIGTOP-1066:
----------------------------------
Update on this.
- Dasha's BIGTOP-1213 patch resolves the sleep issue (removed)
- Still outstanding: pulling in a hard coded hadoop-examples jar so that its
explicit which hadoop-examples jar bigtop is using. I think that will be
easier once the gradle tides come in
> multifilewc and possibly other mapreduce smoke tests rely on mapred: should
> they be separated or replaced?
> ----------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1066
> URL: https://issues.apache.org/jira/browse/BIGTOP-1066
> Project: Bigtop
> Issue Type: Bug
> Reporter: jay vyas
> Priority: Minor
>
> I've updated this ticket to be more focused on a solution rather than
> brainstorming the problem :) ...
> Problem: The use of old tests (i.e. those that use mapred) can cause issues.
> Bigtop gets its hadoop mapreduce tests from the underlying mapreduce library,
> which in some ways is good - it is expected to match the distro - but other
> ways , its bad, because if takes control away from the person running the
> bigtop smokes.
> Solution: Should bigtop have a specific version of mapreduce smokes which it
> runs by linking to the hadoop-examples as maven deps instead of by
> referencing the hadoop-examples jars in the distribution?
> Any thoughts? A patch that implemented this would simply add a pom file
> dependency snippet referencing hadoop-examples, or else, pull the jars down
> some other way, and run them directly rather then referencing
> HADOOP_HOME/examples*jar
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
