From 3d2b40ea3f3317ceba10996750162a113d001c14 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Thu, 5 Sep 2024 12:10:51 -0400 Subject: [PATCH] small change. --- product_docs/docs/pgd/5.6/reference/commit-scopes.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx b/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx index 95554955620..c34ebb784df 100644 --- a/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx @@ -49,7 +49,9 @@ Where `node_group` is the name of a PGD data node group. ## Commit scope targets -Instead of targeting a specific PGD data node group, you can target `ORIGIN_GROUP` to create a rule that applies to the node group of *any* transaction-originating data node in the cluster, simplifying the rule definition by covering multiple groups simultaneously. For example, supposing you have two groups `right_dc` and `left_dc`, instead of having one rule `MAJORITY (left_dc)` and another rule `MAJORITY (right_dc)`, you can just use the one rule `MAJORITY ORIGIN_GROUP` that will apply to both groups. +Instead of targeting a specific PGD data node group, you can target `ORIGIN_GROUP` to create a rule that applies to the node group of *any* transaction-originating data node in the cluster, simplifying the rule definition by covering multiple groups simultaneously. + +For example, supposing you have two groups `right_dc` and `left_dc`, instead of having one rule `MAJORITY (left_dc)` and another rule `MAJORITY (right_dc)`, you can just use the one rule `MAJORITY ORIGIN_GROUP` that will apply to both groups. ## Commit scope groups