openstack/keystone
Code Issues Proposed changes
97431ec99b
keystone/doc/source/contributor/list-truncation.rst
Vishakha Agarwal db57d74fe4 Update filtering-responsibilities and truncation 
This patch updates the change of architecture in keystone by the
removal of controllers.

Change-Id: I19fa04e3293e950d7a33874bc92937c7cbf47176
2020-05-20 16:28:00 +05:30

1.5 KiB
Raw Blame History

Entity list truncation by drivers

Keystone supports the ability for a deployment to restrict the number of entries returned from list operations, typically to prevent poorly formed searches (e.g. without sufficient filters) from becoming a performance issue.

These limits are set in the configuration file, either for a specific driver or across all drivers. A global list_limit set in [DEFAULT] section of keystone is considered in case no limit is set for specific driver. These limits are read at the Manager level and passed into individual drivers as part of the Hints list object. A driver should try and honor any such limit if possible, but if it is unable to do so then it may ignore it (and the truncation of the returned list of entities will happen at the API level by wrap_collection method).