-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RC: RDI in the cloud #570
base: main
Are you sure you want to change the base?
RC: RDI in the cloud #570
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of possible suggestions, but there are also some gltiches that need attention. Otherwise, looking great so far :-)
|
||
Only the following are supported at this time: | ||
|
||
- One source database connected to one target database |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would go with these limitations in this order:
- Redis Cloud Pro tier
- Ingest use case
- AWS platform (source and target database)
- One source database connected to one target database
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
|
||
Using RDI with Redis Cloud simplifies managing your data integration pipeline. No need to worry about hardware or underlying infrastructure, as Redis Cloud manages that for you. Creating the data flow from source to target is much easier, and there are validations in place to reduce errors. | ||
|
||
## Data pipeline architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typically in cloud service, you don't explain about the architecture too much but more about the functionality. I think in this case what matters to the user:
- The fact that it can start with "backfill" process taking a baseline snapshot of the desired data
- then move automatically to track the changes for this dataset
- guaranteed to deliver at least once each record unless the RDI database crushed (and then can go back to baseline)
- can transform relational database rows to Hash or JSON in Redis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure I cover the "backfill" process by using the term "ingest" and the "tracking changes" by talking about "change streaming" - are these meaningfully different terms?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added Hash/JSON in 129d6af.
|
||
To create a new data pipeline, you need to: | ||
|
||
1. [Prepare your source database]({{<relref "/operate/rc/databases/rdi/setup">}}) and any associated credentials. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
except for preparing we need to create the private link and the secret
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that page also includes PrivateLink and creating the credentials secret.
At this point, Redis Cloud will attempt to create your new pipeline. | ||
|
||
Pipelines are created in the background. While they're being created, you aren't allowed to make changes. This process will take some time. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing all the data set selection phases
Missing selecting the Redis data type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's all covered in the Define data pipeline page. If we move it here, this page risks getting too long.
|
||
See the [RDI architecture overview]({{< relref "/integrate/redis-data-integration/architecture#overview" >}}) for more information about CDC. | ||
|
||
## Share source database credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
credentials and TLS certificates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's covered in this section. I thought "credentials" in the header would include certificates without making the header too long.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor things (broken link does need fixing, though) but otherwise looking really good :-)
Select **Add schema** to add additional database schemas. | ||
|
||
Select **Delete** to delete a schema. You must have at least one schema to continue. | ||
|
||
After you've selected the schemas and tables you want to sync, select **Continue**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intended to be a sublist (bulletted)? I definitely think it should be because the formatting currently looks a bit odd without it.
Select **Add schema** to add additional database schemas. | |
Select **Delete** to delete a schema. You must have at least one schema to continue. | |
After you've selected the schemas and tables you want to sync, select **Continue**. | |
- Select **Add schema** to add additional database schemas. | |
- Select **Delete** to delete a schema. You must have at least one schema to continue. | |
- After you've selected the schemas and tables you want to sync, select **Continue**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will be a lot easier to parse once I add screenshots.
|
||
## Pipeline provisioning errors {#errors} | ||
|
||
Add errors here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing you haven't been provided with the list of errors yet :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically, yes. I need to go through the mockups again.
|
||
1. In the [Redis Cloud console](https://cloud.redis.io/), go to your target database and select the **Data Pipeline** tab. | ||
1. Select **Create data pipeline**. | ||
1. Select your source database type. The following database types are supported: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also mention MariaDB and Aurora in the intro page. AFAIK, MariaDB is basically the same as MySQL, so I generally write MySQL/MariaDB together. Is Aurora specific to cloud RDI, with it being an Amazon product? Also, if we do support Aurora for this then do we need some extra instructions for it in the Prepare Source Databases section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yaronp68 - Can you elaborate more on the Aurora inclusion? Is it the same as mySQL/mariaDB, or do we need to add more information as Andy said?
Select **Add schema** to add additional database schema. | ||
|
||
Select **Delete** to delete a schema. You must have at least one schema to continue. | ||
|
||
After you've selected the schemas and tables you want to sync, select **Continue**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sublist again, maybe?
Select **Add schema** to add additional database schema. | |
Select **Delete** to delete a schema. You must have at least one schema to continue. | |
After you've selected the schemas and tables you want to sync, select **Continue**. | |
- Select **Add schema** to add additional database schema. | |
- Select **Delete** to delete a schema. You must have at least one schema to continue. | |
- After you've selected the schemas and tables you want to sync, select **Continue**. |
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One place where a link might not be right but otherwise looks good. I think there are still screenshots and other stuff still to add, so possibly too early to give final approval for the PR.
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
DOC-4137
EDIT: Main staging links:
https://redis.io/docs/staging/DOC-4137/operate/rc/databases/rdi/
https://redis.io/docs/staging/DOC-4137/operate/rc/databases/rdi/define
https://redis.io/docs/staging/DOC-4137/operate/rc/databases/rdi/setup
https://redis.io/docs/staging/DOC-4137/operate/rc/databases/rdi/view-edit