RFE: Add materialized path to project model

Bug #1816109 reported by Lance Bragstad on 2019-02-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Wishlist
Unassigned

Bug Description

To manage hierarchical multi-tenancy (HMT) effectively the introduced adjacency list field 'parent_id' is not enough and requires recursion to traverse the tree, which can negatively impact performance in deployments the complex hierarchical structures.

The materialized path concept gives us the ability to find all ascendants and descendants of a particular node in a single request operation.

Lance Bragstad (lbragstad) wrote :
tags: added: hierarchical-multitenancy performance
tags: added: sql
Changed in keystone:
status: New → Triaged
importance: Undecided → Wishlist
Lance Bragstad (lbragstad) wrote :

The following patches work towards this initiative:

Materialized path mixin and field for hierarchical models: https://review.openstack.org/249847
SQLAlchemy column type for materialized path: https://review.openstack.org/251445
Materialized path convenience wrapper: https://review.openstack.org/251455
Use path hybrid property in query filtering: https://review.openstack.org/251513

tags: added: rfe
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers