summaryrefslogtreecommitdiff
path: root/releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml')
-rw-r--r--releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml16
1 files changed, 16 insertions, 0 deletions
diff --git a/releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml b/releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml
new file mode 100644
index 000000000..3d91f6231
--- /dev/null
+++ b/releasenotes/notes/change-db-access-pattern-for-node-lists-a333dd9c5afa737d.yaml
@@ -0,0 +1,16 @@
+---
+upgrade:
+ - |
+ The query pattern for the database when lists of nodes are retrieved has
+ been changed to a more efficient pattern at scale, where a list of nodes
+ is generated, and then additional queries are executed to composite this
+ data together. This is from a model where the database client in the
+ conductor was having to deduplicate the resulting data set which is
+ overall less efficent.
+other:
+ - |
+ The default database query pattern has been changed which will result
+ in additional database queries when compositing lists of ``nodes``
+ by separately querying ``traits`` and ``tags``. Previously this was a
+ joined query which requires deduplication of the result set before
+ building composite objects.