[
https://issues.apache.org/jira/browse/CLOUDSTACK-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476634#comment-13476634
]
Alena Prokharchyk commented on CLOUDSTACK-332:
----------------------------------------------
For qa - all commands mentioned in 2 prev comments have to be tested. Also test
that the count is right in JSON and XML response.
The rest of the commands will be fixed in the next release - as a part of
refactoring Min Chen is doing for Search. The reasons why it wasn't fixed with
the current commits:
* for some commands multiple DB queries are done to get the result set + the
result set is being modified later on. So with the current logic it's hard to
figure out what is the actual number of objects in the DB matching the search
criteria passed in API request. Only when Min puts her fixes for Search
Engine, it would be possible to resolve the rest of the API commands.
> "count" property in list* API response should be equal to how many entries in
> database, not how many objects in API response
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-332
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-332
> Project: CloudStack
> Issue Type: Bug
> Components: Management Server
> Affects Versions: 4.0.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Fix For: 4.1.0
>
>
> e.g. If there are 8500 entries in database satisfying the search criteria
> (parameters in list api call), list* API returns 500 objects in API response,
> "count" property in API response should be 8500 instead of 500.
--
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
