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

ASF GitHub Bot commented on TEZ-3848:
-------------------------------------

GitHub user jacobtolar opened a pull request:

    https://github.com/apache/tez/pull/20

    [TEZ-3848] Tez local mode doesn't localize distributed cache files

    @jteagles 
    
    See https://issues.apache.org/jira/browse/TEZ-3848

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jacobtolar/tez TEZ-3848

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tez/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #20
    
----
commit fbf77dbfa3c1d02b5a7de570fdade74a88bc370c
Author: Jacob Tolar <[email protected]>
Date:   2017-10-02T22:33:57Z

    [TEZ-3848] Tez local mode doesn't localize distributed cache files

----


> Tez Local mode doesn't localize distributed cache files
> -------------------------------------------------------
>
>                 Key: TEZ-3848
>                 URL: https://issues.apache.org/jira/browse/TEZ-3848
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jacob Tolar
>
> Tez doesn't symlink LocalResources into place in LocalContainerLauncher.
> In YARN mode, Yarn takes care of this when it launches the container. But in 
> local mode, if you're depending on a file existing in the distributed cache, 
> it's never symlinked into place (so you're out of luck).
> We test our pig scripts in local mode and have some tools to set up the 
> distributed cache the same way it would work in production. This works fine 
> in Mapreduce mode but are unable to use Pig + Tez local mode for testing due 
> to this problem.
> I have a fix working and will submit a PR once I rebase it.
> [~jeagles] [[email protected]]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to