[
https://issues.apache.org/jira/browse/MAPREDUCE-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185003#comment-16185003
]
Hadoop QA commented on MAPREDUCE-6458:
--------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} MAPREDUCE-6458 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | MAPREDUCE-6458 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12751766/MAPREDUCE-6458.00.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7161/console |
| Powered by | Apache Yetus 0.5.0 http://yetus.apache.org |
This message was automatically generated.
> Figure out the way to pass build-in classpath (files in distributed cache,
> etc.) from parent to spawned shells
> --------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6458
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6458
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Junping Du
> Assignee: Dustin Cote
> Attachments: MAPREDUCE-6458.00.patch
>
>
> In MAPREDUCE-6454 (target for branch-2.x), we provide a way with constraints
> to pass built-in classpath from parent to child shell, via HADOOP_CLASSPATH,
> so jars in distributed cache can still work in child tasks. In trunk, we may
> think some way different, like: involve additional env var to safely pass
> build-in classpath.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]