[
https://issues.apache.org/jira/browse/TEZ-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028226#comment-14028226
]
Bikas Saha commented on TEZ-1193:
---------------------------------
I fully agree with the developer perspective and your contribution in this area
is very useful. The reason we prefer an override vs making it optional is that
in our experience with configuration values its easy to make errors of omission
vs errors of commission. Which means its easy to make a mistake by forgetting
to specify something vs explicitly specifying something. tez.lib.uris is the
recommended method for people using tez and so we dont want that to be subject
to errors of omission. In a dev envrironment, the dev should be able to
override this explicitly and get advantage you mention. Does that help clarify.
> Make 'tez.lib.uris' dependency optional
> ---------------------------------------
>
> Key: TEZ-1193
> URL: https://issues.apache.org/jira/browse/TEZ-1193
> Project: Apache Tez
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Attachments: TEZ-1193.patch
>
>
> Hadoop/YARN provides a mechanism to setup a runtime classpath of Tez/YARN job
> through LocalResources. Tez exposes setting of LocalResources through
> AMConfiguration and Vertex thuis allowing AM and ACs have its independent
> classpath which can include Tez (depending on how Tez job is written). This
> means that setting _tez.lib.uris_ and installing Tez all together should be
> optional since its libraries could be easily propagated during job submission.
> It also ensures that the Tez libraries that were used during build are the
> same that are used during the runtime.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
