Extend filtering into the identity backends wherever possible to improve scaling and performance
Registered by
Henry Nash
Filtering is currently done at the controller level, which means that for larger collections, the entire set of entities must be retrieved from the backend before filtering can occur. This leads to serious performance problems.
Filtering should be enabled in those backends that can use the underlying store (e.g. SQL, LDAP) to filter-at-source.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Henry Nash
- Direction:
- Needs approval
- Assignee:
- Henry Nash
- Definition:
- Pending Approval
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Henry Nash
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Implement filter support in driver backends
Gerrit topic: https:/
Gerrit topic: https:/
(?)