Skip to content

Commit ff38ca5

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 70c1f7c commit ff38ca5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ weight: 30
1515
---
1616

1717

18-
The RDI pipelines support two separate row formats which can be specified in the `source` section of the job file:
18+
The RDI pipelines support two separate row formats which you can specify in the `source` section of the job file:
1919

20-
- `basic` - this is the default one, when no `row_format` is specified. It contains only the current value of the row
21-
- `full` - you get a full representation of the row, including the key, the before and after values, the operation code, etc.
20+
- `basic` - (Default) Contains the current value of the row only.
21+
- `full` - Contains all information available for the row, including the key, the before and after values, and the operation code.
2222

2323
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.
2424
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.

0 commit comments

Comments
 (0)