[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390092#comment-15390092
 ] 

Haibo Chen edited comment on MAPREDUCE-6741 at 7/22/16 7:43 PM:
----------------------------------------------------------------

Good point! I have not thought about updating the jobconf file in HDFS.  A 
question that may or may not be relevant to this. I notice that for every job 
there are always two job conf files.  One file, named job.xml, is submitted by 
the client and localized as task container resource. The other, named 
$(jobid)_conf.xml,  is created by JobHistoryEventHandler and loaded by JHS. Any 
particular reason why we have two files lying around for one job? 


was (Author: haibochen):
Good point! I have not thought about updating the jobconf file in HDFS.  A 
question that may or may not be relevant to this. I notice that for every job 
there are always two job conf files.  One file, named job.xml, is submitted by 
the client and localized as task container resource. The other, named 
{jobid}_conf.xml,  is created by JobHistoryEventHandler and loaded by JHS. Any 
particular reason why we have two files lying around for one job? 

> add JHS support to hide job conf properties from Web UI
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-6741
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6741
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 2.7.2
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>
> JHS today displays all Job conf properties in Web UI directly. Users may have 
> some credentials or any sensitive information they added to the job conf but 
> do not want to be shown in Web UI. It'd be nice if we can allow users to 
> specify a set of properties which JHS will filter out when Job conf is 
> displayed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to