Bug 1041867 - [RFE][keystone]: Allow additional data to be requested for API GET calls to minimise N+1 performance problem
Summary: [RFE][keystone]: Allow additional data to be requested for API GET calls to m...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:47 UTC by RHOS Integration
Modified: 2016-02-03 05:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:34:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:47:26 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/extended-get-apis.

Description:

Like many relational-defined repositories, obtaining data via the identity api can sometmes suffer from what is known as the "N+1" problem.  This is when you want to list all objects of a certain class (e.g. users, projects) and also get related information (e.g roles) - which can often result in one GET for the list of objects itself, followed by GET's for each item in the list to obtain the related data.  Often, such a query could be implemented in one go by the underlying storage layer (e.g. SELECT/JOIN in SQL) if only you could express the query correctly via the REST API.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.