File tree Expand file tree Collapse file tree 1 file changed +5
-1
lines changed
content/integrate/redis-data-integration/data-pipelines Expand file tree Collapse file tree 1 file changed +5
-1
lines changed Original file line number Diff line number Diff line change @@ -64,7 +64,9 @@ The job must include the following attributes in the `nest` block:
64
64
- `parent` : This specifies the RDI data stream for the parent entities. Typically, you only
65
65
need to supply the parent `table` name, unless you are nesting children under a parent that comes from
66
66
a different source database. If you do this then you must also specify `server_name` and
67
- ` schema` attributes.
67
+ ` schema` attributes. Note that this attribute refers to a Redis *key* that will be added to the target
68
+ database, not to a table you can access from the pipeline. See [Using nesting](#using-nesting) below
69
+ for the format of the key that is generated.
68
70
- `nesting_key` : The field of the child entity that stores the unique ID (primary key) of the child entity.
69
71
- `parent_key` : The field in the parent entity that stores the unique ID (foreign key) of the parent entity.
70
72
- `child_key` : The field in the child entity that stores the unique ID (foreign key) of the parent entity.
@@ -75,6 +77,8 @@ The job must include the following attributes in the `nest` block:
75
77
- `structure` : (Optional) The type of JSON nesting structure for the child entities. Currently, only a JSON map
76
78
is supported so if you supply this attribute then the value must be `map`.
77
79
80
+ # # Using nesting
81
+
78
82
There are several important things to note when you use nesting :
79
83
80
84
- When you specify `nest` in the job, you must also set the `data_type` attribute to `json` and
You can’t perform that action at this time.
0 commit comments