[
https://issues.apache.org/jira/browse/TEZ-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074578#comment-14074578
]
Hitesh Shah commented on TEZ-1205:
----------------------------------
The property "tez.task.additional.launch.cmd-opts" needs to be tied with the
property that specifies on which vertices/tasks the additional cmd-opts need to
be added. If both have a similar prefix, that may help ( or something in the
property name to define the relationship). Documentation should also clarify
the same.
"additional" does not help much when trying to explain to a user why do we have
both a cmd-opts and an additional "additional.cmd-opts"
> Remove "profiling" keyword from APIs/configs
> ---------------------------------------------
>
> Key: TEZ-1205
> URL: https://issues.apache.org/jira/browse/TEZ-1205
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Gopal V
> Priority: Blocker
>
> Given that the current functionality to support profiling actually just
> implies augmenting of command line options for a specified set of tasks, we
> can word the APIs and configs to be more general purpose.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
