[
https://issues.apache.org/jira/browse/TEZ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167657#comment-14167657
]
Hitesh Shah commented on TEZ-1646:
----------------------------------
It probably will be a problem in cases where the tarball approach is not used.
I am guessing there were reasons why MR had config support for user classpath
first/last which may be useful in some cases.
However, even if we add the additional classpath at the very top, it still
raises concerns on whether a vertex's local resources should be before/after a
statically configured classpath.
For now, I think I prefer retaining the current patch structure and iterating
on it if there are concerns raised later.
> Add support for augmenting classpath via configs
> ------------------------------------------------
>
> Key: TEZ-1646
> URL: https://issues.apache.org/jira/browse/TEZ-1646
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-1646.1.patch, TEZ-1646.2.patch, TEZ-1646.3.patch,
> TEZ-1646.4.patch
>
>
> In some cases, users may need to augment the framework classpath to add
> locally deployed/installed resources to the classpath. For examples, where
> resources are not deployed via yarn local resources but via more conventional
> means such as rpms, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
