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

Hudson commented on HDDS-1455:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16474 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16474/])
HDDS-1455. Inconsistent naming convention with Ozone Kerberos (github: rev 
a96d16a843c804b01ccba530172a40fc16647385)
* (edit) hadoop-hdds/docs/content/SetupSecureOzone.md
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/scm/ScmConfigKeys.java
* (edit) hadoop-hdds/common/src/main/resources/ozone-default.xml
* (edit) hadoop-ozone/dist/src/main/compose/ozonesecure/docker-config
* (edit) hadoop-ozone/dist/src/main/compose/ozonesecure-mr/docker-config


> Inconsistent naming convention with Ozone Kerberos configuration
> ----------------------------------------------------------------
>
>                 Key: HDDS-1455
>                 URL: https://issues.apache.org/jira/browse/HDDS-1455
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Eric Yang
>            Assignee: Xiaoyu Yao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.4.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In SetupSecureOzone.md, the naming convention for keytab files are different 
> from code.
> {code}
> hdds.scm.http.kerberos.keytab
> ozone.om.http.kerberos.keytab
> {code}
> In ozone-default.xml, it is looking for:
> {code}
> hdds.scm.http.kerberos.keytab
> ozone.om.http.kerberos.keytab.file
> {code}
> For the non http version of keytab, they are branded as:
> {code}
> hdds.scm.kerberos.keytab.file
> ozone.om.kerberos.keytab.file
> {code}
> It is best to shorten the name to remove .file suffix from the code to be 
> consistent with Hadoop naming convention.  The second nitpick is hdds and 
> ozone prefix.  Is there a good reason to have distinct prefix for both that 
> work closely together?  How about hadoop.ozone prefix?  From usability point 
> of view, the current prefix are very confusing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to