You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Xi Wang (JIRA)" <ji...@apache.org> on 2014/06/27 04:04:25 UTC

[jira] [Commented] (AMBARI-6301) Hosts page: RAM filter not worked for exact match

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

Xi Wang commented on AMBARI-6301:
---------------------------------

The solution:
If the user type in an exact value, then convert it to a range of numbers, and turn into a range query to server.
For example, user enter 1.83 G, will pass a query to filter hosts with memory from 1.825000 to 1.834999 GB. 
For example, user enter 1.8 KB(MB), will pass a query to filter hosts with memory from 1.75000 to 1.84999 KB(MB).

So Current behavior:
Say I have three hosts with RAM 1.83G on Hosts page.
Type in: 1.83 , Filtered Content: 3 hosts
Type in: 1.828 , Filtered Content: 3 hosts
Type in: 1.831 , Filtered Content: 3 hosts
Type in: 1.84 , Filtered Content: 0 hosts
Type in: 1.82 , Filtered Content: 0 hosts
Type in: 1.83k , Filtered Content: 0 hosts
Type in: 1.83m , Filtered Content: 0 hosts

> Hosts page: RAM filter not worked for exact match
> -------------------------------------------------
>
>                 Key: AMBARI-6301
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6301
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.1
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>            Priority: Critical
>             Fix For: 1.6.1
>
>         Attachments: AMBARI-6301.patch
>
>
> On hosts page, RAM filter not worked for exact match.
> If enter expressions such as '>1' or '<2' the filter works. But if enter exact match filter like '1.83' the filter does not work.
> Second problem is that usage of the filter is not intuitive. We should have hover text explaining how to use this filter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)