yahoo-eng-team team mailing list archive

[Dolph Mathews <1480787@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1451402 ***
    https://bugs.launchpad.net/bugs/1451402

Pagination has not been implemented. To do so, it must be entirely
controlled by the server (not the API client) due to the requirement to
support multiple backends (SQL vs LDAP, for example). The page &
per_page scheme will not work for all drivers, and thus cannot be
controlled by the end user, and is thus not a documented API. v3 does
provide "next" and "previous" links for pagination purposes, but they
are not currently populated. The closest behavior we have right now is
server-defined limits on the number of resources returned by the backend
in a single collection, which is controlled by keystone.conf list_limit.

I've marked this bug as a dupe of 1451402 and re-opened that bug against
openstack-api-site. It must have slipped my bug radar in the leadup to
the summit; my apologies!

** This bug has been marked a duplicate of bug 1451402
   v3 - pagination in GET services does not work

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1480787

Title:
  Pagination not working in Kilo

Status in Keystone:
  New

Bug description:
  I have created more than 100 users, but while I execute following command
    GET http://<url>:35357/v3/users?page=2\&per_page=35 -v 
  I am getting list of all users.

  I found this bug  https://bugs.launchpad.net/bugs/1451402 has been
  expired due to inactivity.

  Can anyone confirm if pagination is supported in Identity API v3 or do
  I need to configure anything, so that pagination works?

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1480787/+subscriptions