You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "echohlne (Jira)" <ji...@apache.org> on 2020/08/18 15:27:00 UTC
[jira] [Updated] (AMBARI-25546) The maximum parameter on the
heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
echohlne updated AMBARI-25546:
------------------------------
Summary: The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing)
> The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
> -----------------------------------------------------------------------------------------------
>
> Key: AMBARI-25546
> URL: https://issues.apache.org/jira/browse/AMBARI-25546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.4
> Reporter: echohlne
> Priority: Minor
> Fix For: 2.7.5
>
> Attachments: heatmap-NaN-screentshot.png, heatmap-negative-screentshot.png
>
>
> We like this open source software very much, but we found a little problem in use.
> the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing which is not very kindly.
> examples has been shown in the attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)