yunikorn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilfred Spiegelenburg (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (YUNIKORN-113) [webapp] Change default value for maximum queue capacity
Date Fri, 01 May 2020 07:00:11 GMT

     [ https://issues.apache.org/jira/browse/YUNIKORN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wilfred Spiegelenburg resolved YUNIKORN-113.
--------------------------------------------
    Fix Version/s: 0.9
       Resolution: Fixed

change committed based on [~akhilpb] review

> [webapp] Change default value for maximum queue capacity
> --------------------------------------------------------
>
>                 Key: YUNIKORN-113
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-113
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: webapp
>            Reporter: Kinga Marton
>            Assignee: Kinga Marton
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9
>
>         Attachments: Screenshot 2020-04-27 at 10.10.48.png
>
>
> If there is no maximum capacity set for a queue, in the response from the backend there
will be an empty string. However in the webapp 0 value is displayed, what is wrong, because
0 means that the resource is not available.
> We should change its default value to "N\A" or something with the meaning of not available/not
set instead of setting it to 0.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org


Mime
View raw message