Skip to content

Commit 4298b06

Browse files
Update content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-row-format.md
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent ff38ca5 commit 4298b06

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-row-format.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ The RDI pipelines support two separate row formats which you can specify in the
2020
- `basic` - (Default) Contains the current value of the row only.
2121
- `full` - Contains all information available for the row, including the key, the before and after values, and the operation code.
2222

23-
The `full` row format is useful when you want to access the metadata associated with the row, such as the operation code, the before and after values, etc.
24-
Based on the used row format, the structure of the data passed to the `transform` and `output` sections is different and the keys should be referenced accordingly to the chosen row format.
23+
The `full` row format is useful when you want to access the metadata associated with the row, such as the operation code, and the before and after values.
24+
The structure of the data passed to the `transform` and `output` sections is different depending on the row format you choose. Consider which row format you are using when you reference keys.
2525
The following two examples demonstrate the difference between the two row formats.
2626

2727
## Default row format

0 commit comments

Comments
 (0)