You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/12/07 01:50:35 UTC

[jira] [Resolved] (CLOUDSTACK-5390) listNetworks: pageSize and page parameters are not applied properly

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

Alena Prokharchyk resolved CLOUDSTACK-5390.
-------------------------------------------

    Resolution: Fixed

> listNetworks: pageSize and page parameters are not applied properly
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5390
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5390
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.3.0
>
>
> ListNetworks call does numerous calls to the DB to get diff kinds of networks based on search criteria (Isolated and Shared). The result sets are combined and returned to the API. As page/pageSize parameters are passed only to the DB call, they are not respected while generating the final set.
> There can be 2 ways to fix the problem:
> 1) generate only one call to the DB
> or
> 2) After the result set is finalized, apply the pagination to it. 
> I would go with #2 as changing the db call can introduce regressions plus its very hard to achieve given the number of joins happening based on the search criteria. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)