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

Robert Joseph Evans commented on MAPREDUCE-4644:
------------------------------------------------

We need to be in the process of separating out true unit test from system and 
integration tests.  Unit tests should run fast and are something that we can do 
for all components as part of the pre-commit build.  If the test is full 
featured enough that it could be called as a "tool" then there is no way that 
it is a true unit test. I am +1 for moving those out to be part of a tools or 
examples package somewhere.

We also need to look at cleaning up our classpaths.  Separating each tool out 
into a directory with a full list of its dependencies seems like a reasonable 
solution.  It is what Oozie asks users to do for their work flows and seems to 
work fairly well.  But that starts to sound like a larger effort then moving a 
few classes around and splitting a launcher into two.  I think it is something 
that needs to be done, but perhaps needs some design work, especially in 
relation to how we may want to do dependency isolation in the future with OSGi 
or something else.  Alejandro, I know you have been looking at and thinking 
about the classpath issue with YARN/MR, and how we should package things a lot 
already. MAPREDUCE-3745, HADOOP-7935, and MAPREDUCE-4421 do we need another 
JIRA explicitly for tools?  How do we handle the case of a tool having a 
map/reduce dependency now that the MR code is going to be separated out so that 
we can use a different version of MR?  Does that mean that they have to provide 
their own tools with a MR dependency and a config to point to them?  It just 
seems like a change like this needs a full design. 
                
> mapreduce-client-jobclient-tests do not run from dist tarball
> -------------------------------------------------------------
>
>                 Key: MAPREDUCE-4644
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4644
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: build, test
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Priority: Blocker
>
> The mapreduce jobclient tests rely on junit which is missing from the dist 
> tarball.  This prevents running often-used tests like sleep jobs.

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