[
https://issues.apache.org/jira/browse/AMBARI-17132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321909#comment-15321909
]
Hudson commented on AMBARI-17132:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #5038 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5038/])
AMBARI-17132 - Typing the whole component name vs selecting drop down (rzang:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f9d9ff1b3808710b8a00f1a3b72f75418b2676eb])
* ambari-web/app/templates/main/host/combo_search_box.hbs
* ambari-web/app/messages.js
* ambari-web/app/views/main/host/combo_search_box.js
> Typing the whole component name vs selecting drop down filter in hosts page
> gives 2 different results
> -----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-17132
> URL: https://issues.apache.org/jira/browse/AMBARI-17132
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17132.patch
>
>
> Directly type in namenode:all and selecting NameNode:All and press ENTER
> generates different returns. This is because when manually type in, it has to
> match all cases. User should alway select an option instead of forcing facet
> generation from manually typed in content. Show alert message when there's no
> matching category.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
