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

Hudson commented on AMBARI-16728:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4888 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4888/])
AMBARI-16728. Ambari APIs should allow using case insensitive host 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ae6d0106751467a1a38fb6e60213fb0f09ba692c])
* 
ambari-server/src/test/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImplTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/predicate/QueryParser.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/predicate/QueryParserTest.java


> Ambari APIs should allow using case insensitive host names(for SmartSense)
> --------------------------------------------------------------------------
>
>                 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)

Reply via email to