[jira] [Updated] (MAPREDUCE-5097) Job.addArchiveToClassPath is ignored when running job with LocalJobRunner

["Alex Baranau (JIRA)" <ji...@apache.org>]

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

Alex Baranau updated MAPREDUCE-5097:
------------------------------------

    Attachment: MAPREDUCE-5097-ugly-test.patch
                MAPREDUCE-5097.patch

Attached tiny patch (MAPREDUCE-5097.patch).

Also tried to show the test case scenario that fails without the patch (MAPREDUCE-5097-ugly-test.patch). It is ugly: it actually just shows that when job classes are not in classpath then adding the jar using addArchiveToClassPath has no effect. The test should be better. I will try to figure one out when I have more time.. if this is really needed: the fix is pretty simple (if I got it right).
                
> Job.addArchiveToClassPath is ignored when running job with LocalJobRunner
> -------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5097
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5097
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Alex Baranau
>            Assignee: Alex Baranau
>            Priority: Minor
>         Attachments: MAPREDUCE-5097.patch, MAPREDUCE-5097-ugly-test.patch
>
>
> Using external dependency jar in mr job. Adding it to the job classpath via Job.addArchiveToClassPath(...) doesn't work when running with LocalJobRunner (i.e. in unit test). This makes it harder to unit-test such jobs (with third-party runtime dependencies).

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