cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3537) [UI] - when pass pageSize to the list* api calls, check against global config "default.page.size"
Date Mon, 19 Aug 2013 21:21:48 GMT

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

Alena Prokharchyk updated CLOUDSTACK-3537:
------------------------------------------

    Fix Version/s:     (was: 4.2.0)
                   Future
    
> [UI] - when pass pageSize to the list* api calls, check against global config "default.page.size"
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3537
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3537
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Brian Federle
>             Fix For: Future
>
>
> Global config "default.page.size" defines max allowed pageSize for list* api calls. If
no pageSize specified in the call, then its being defaulted to this global config. When pageSize
is passed to the call, then it shouldn't be greater than default.page.size.
> The bug is: UI passed pageSize to the number of API calls w/o verifying whether this
number is less than default.page.size allows. And it ends up with the errors on the API side
"Page size can't exceed max allowed page size value"
> Suggested fix: when UI passes pageSize param to the list* API call:
> * verify its value against default.page.size
> * if its <=, pass it to the call
> * if its >, then pass default.page.size to the call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message