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

ASF GitHub Bot logged work on HDDS-1455:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Apr/19 05:43
            Start Date: 29/Apr/19 05:43
    Worklog Time Spent: 10m 
      Work Description: xiaoyuyao commented on issue #762: HDDS-1455. 
Inconsistent naming convention with Ozone Kerberos configu…
URL: https://github.com/apache/hadoop/pull/762#issuecomment-487457038
 
 
   /retest
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 234320)
    Time Spent: 50m  (was: 40m)

> 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
>          Time Spent: 50m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to