Skip to content

Commit 756b7d4

Browse files
Update content/integrate/redis-data-integration/data-pipelines/data-denormalization.md
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent 96c0caf commit 756b7d4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/integrate/redis-data-integration/data-pipelines/data-denormalization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ You can also use custom keys for the parent entity, as long as you use the same
106106

107107
## Joining one-to-many relationships
108108

109-
To join one-to-many relationships you can use the *Nesting* strategy.
109+
To join one-to-many relationships, you can use the *Nesting* strategy.
110110
With it, the parent object (the "one") is represented as a JSON document with the children (the "many") nested inside a JSON map attribute in the parent. The diagram below shows a nesting with the child objects in a map called `InvoiceLineItems`:
111111

112112
{{< image filename="/images/rdi/ingest/nest-flow.webp" width="500px" >}}

0 commit comments

Comments
 (0)