[
https://issues.apache.org/jira/browse/OOZIE-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023168#comment-16023168
]
Rohini Palaniswamy commented on OOZIE-2890:
-------------------------------------------
bq. It's very hacky and encourages the user to load in incompatible/conflicting
jars and rely on classpath ordering, which is bad.
Problem is there are lot of users who are already using this feature.
Removing support means lot of running jobs will break. When we do the Oozie on
YARN upgrade, my expectation is all coordinators continue to run without issues
and there is no migration effort for the user or behavior change except for the
fact that the launcher job UI will look different.
> Implement the equivalent of mapreduce.task.classpath.user.precedence
> --------------------------------------------------------------------
>
> Key: OOZIE-2890
> URL: https://issues.apache.org/jira/browse/OOZIE-2890
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Peter Bacsko
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
