DOC-3907 added transform info lost from the old docs #337
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andy-stark-redis
added
the
documentation
Contributor
yaronp68
requested changes
Jun 19, 2024
Collaborator
yaronp68
left a comment
yaronp68
left a comment
There was a problem hiding this comment.
the content is mish-mashed between config.yaml and job
| and add it to a Redis target database. | ||
| - *Write-behind* pipelines capture data from a Redis source database | ||
| and add it to an external target database. | ||
| - [*Write-behind*]({{< relref "/integrate/redis-data-integration/write-behind/architecture" >}}) |
| ## Overview | ||
|
|
||
| Pipelines *transform* the data that RDI captures from the source into a Redis data | ||
| type that is suitable for the target. RDI provides a default transformation |
Collaborator
There was a problem hiding this comment.
This is not accurate:
RDI will translate one record of source to Redis Hash or Redis JSON and will translate the source fields to Hash fields or JSON attributes.
With RDI pipeline you can do much more, using prebuild transformation and filtering blocks that you configure using expressions
Contributor
Author
There was a problem hiding this comment.
Hopefully improved now.
| that require no coding. | ||
|
|
||
| The data tranformation involves two separate stages. First, the data ingested by | ||
| [Debezium](https://debezium.io/) is automatically transformed to a Redis JSON format. Then, |
Collaborator
There was a problem hiding this comment.
Suggested change
| [Debezium](https://debezium.io/) is automatically transformed to a Redis JSON format. Then, | |
| [Debezium](https://debezium.io/) is automatically transformed to a JSON format. Then, |
| [hashes]({{< relref "/develop/data-types/hashes" >}}), | ||
| [sets]({{< relref "/develop/data-types/sets" >}}), or | ||
| [streams]({{< relref "/develop/data-types/streams" >}}) | ||
| . |
Collaborator
There was a problem hiding this comment.
now we also support sorted sets and strings
yaronp68
approved these changes
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added information about transformations that was present in the old docs but lost from the new ingest docs.
I've dropped old sections that referred to MongoDB and Cassandra, since I believe these aren't available as ingest sources currently. I've also assumed that Redis is the only available target database type for ingest.