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

Hari Sekhon edited comment on HADOOP-14665 at 11/10/17 1:39 PM:
----------------------------------------------------------------

Ok I didn't see that documented in the top few google hits, maybe it's just not 
widely known, and since it looks like a flat unix config, hash comments were 
expected.

I still think supporting hash comments would be more intuitive as in management 
consoles all the files which have free form configuration boxes are in unix 
config file format and use hash comments.


was (Author: harisekhon):
Ok I didn't see that documented in the top few google hits and since it looks 
like a flat unix config, hash comments were expected.

I still think supporting hash comments would be more intuitive as in management 
consoles all the files which have free form configuration boxes are in unix 
config file format and use hash comments.

> Support # hash prefix comment lines in auth_to_local mapping rules
> ------------------------------------------------------------------
>
>                 Key: HADOOP-14665
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14665
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.7.3
>         Environment: HDP 2.6.0 + Kerberos
>            Reporter: Hari Sekhon
>
> Request to add support for # hash prefixed comment lines in Hadoop's 
> auth_to_local mappings rules so I can comment what rules I've added and why 
> inline to the rules like with code (useful when supporting multi-directory 
> mappings).
> It should be fairly easy to implement, just string strip all lines from # to 
> end, trim whitespace and then exclude all blank / whitespace lines, I do this 
> in tools I write all the time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to