[
https://issues.apache.org/jira/browse/OOZIE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494285#comment-13494285
]
Mona Chitnis commented on OOZIE-1015:
-------------------------------------
Thanks Harsh,
1. Only difference is HADOOP_JOB_TRACKER (and _2) in JAE are private. Changing
those to public seems ok right? Then better not to bring in any confusing
XOozieClient parameters.
2. Seems doable to me. Will assess impact in other places in code and will need
end-to-end test just to be sure.
> HadoopAccessorService jobtracker validation should not have hardcoded conf key
> ------------------------------------------------------------------------------
>
> Key: OOZIE-1015
> URL: https://issues.apache.org/jira/browse/OOZIE-1015
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
> Attachments: OOZIE-1015.patch
>
>
> While validating the jobtracker address against whitelist in
> HadoopAccessorService, the conf key to be looked up is a string value
> "mapred.job.tracker". Instead we should use static variables for robustness
> (mapred.job.tracker for hadoop-1 and yarn.resourcemanager.address for
> hadoop-2)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
