[jira] [Commented] (AMBARI-16728) Ambari APIs should allow using case insensitive host names

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-16728:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12805230/AMBARI-16728.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.view.persistence.DataStoreImplTest
                  org.apache.ambari.server.upgrade.UpgradeCatalog240Test

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6917//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6917//console

This message is automatically generated.

> Ambari APIs should allow using case insensitive host names
> ----------------------------------------------------------
>
>                 Key: AMBARI-16728
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16728
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16728.patch
>
>
> Ambari stores all hostnames in lower-case irrespective of the case in name associated with the host. While this is OK for internal usage it causes confusion to the users or the tools that look up hostname using standard commands such as"hostname -f".
> The API should be modified to allow hostnames in case insensitive fashion. E.g.
> * api/v1/hosts/HostA and api/v1/hosts/hosta both should point to the same host
> * calls that user filter where they specify hostnames should also allow case insensitive comparison



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