|
| 1 | +--- |
| 2 | +Title: View and edit data pipeline |
| 3 | +alwaysopen: false |
| 4 | +categories: |
| 5 | +- docs |
| 6 | +- operate |
| 7 | +- rc |
| 8 | +description: Edit and observe your data pipeline. |
| 9 | +hideListLinks: true |
| 10 | +weight: 4 |
| 11 | +--- |
| 12 | + |
| 13 | +You can use the **Data pipeline** tab in your database to view and edit it. |
| 14 | + |
| 15 | +The **Data pipeline** tab gives an overview of your data pipeline and lets you view your data stream metrics. |
| 16 | + |
| 17 | +## Edit data pipeline |
| 18 | + |
| 19 | +To change the data you want to ingest from the data pipeline: |
| 20 | + |
| 21 | +1. From the **Data pipeline** tab, select **Edit**. |
| 22 | + |
| 23 | +1. For the **Configure a new pipeline** option, select the Redis data type to write keys to the target. You can choose **Hash** or **JSON**. |
| 24 | + |
| 25 | + Select **Continue**. |
| 26 | + |
| 27 | +1. Select the schema and tables you want to migrate to the target database from the **Source data selection** list. You can select any number of columns from a table. |
| 28 | + |
| 29 | + If any tables are missing a unique constraint, the **Missing unique constraint** list will appear. Select the columns that define a unique constraint for those tables from the list. |
| 30 | + |
| 31 | + Select **Add schema** to add additional database schema. |
| 32 | + |
| 33 | + Select **Delete** to delete a schema. You must have at least one schema to continue. |
| 34 | + |
| 35 | + After you've selected the schemas and tables you want to sync, select **Continue**. |
| 36 | + |
| 37 | +1. Review the tables you selected in the **Summary** and select how you want to update the data pipeline: |
| 38 | + |
| 39 | + - **Apply to new data changes only**: The data pipeline will only synchronize new updates to the schema and tables selected. The data pipeline will not ingest any data from new schemas or tables that are selected. |
| 40 | + - **Reset pipeline (re-process all data)**: The data pipeline will re-ingest all of the selected data. |
| 41 | + - **Flush cached data and reset pipeline**: The data pipeline will flush the target Redis database, and then re-ingest all of the selected data from the source database. |
| 42 | + |
| 43 | +1. Select **Apply changes**. |
| 44 | + |
| 45 | +At this point, the data pipeline will apply the changes. If you selected **Reset pipeline** or **Flush cached data and reset pipeline**, the data pipeline will ingest data from the source database to the target database. After this initial sync is complete, the data pipeline enters the *change streaming* phase, where changes are captured as they happen. |
| 46 | + |
| 47 | +If you selected **Apply to new data changes only**, the data pipeline will enter the *change streaming* phase without ingesting the data. |
| 48 | + |
| 49 | +## Reset data pipeline |
| 50 | + |
| 51 | +To reset the data pipeline and restart the ingest process: |
| 52 | + |
| 53 | +1. From the **Data pipeline** tab, select **More actions**, and then **Reset pipeline**. |
| 54 | + |
| 55 | +1. If you want to flush the database, check **Flush target database**. |
| 56 | + |
| 57 | +1. Select **Reset data pipeline**. |
| 58 | + |
| 59 | +At this point, the data pipeline will re-ingest data from the source database to your target Redis database. |
| 60 | + |
| 61 | +## Stop and restart data pipeline |
| 62 | + |
| 63 | +To stop the data pipeline from synchronizing new data: |
| 64 | + |
| 65 | +1. From the **Data pipeline** tab, select **More actions**, and then **Stop pipeline**. |
| 66 | + |
| 67 | +1. Select **Stop data pipeline** to confirm. |
| 68 | + |
| 69 | +Stopping the data pipeline will suspend data processing. To restart the pipeline from the **Data pipeline** tab, select **More actions**, and then **Start pipeline**. |
| 70 | + |
| 71 | +## Delete pipeline |
| 72 | + |
| 73 | +To delete the data pipeline: |
| 74 | + |
| 75 | +1. From the **Data pipeline** tab, select **More actions**, and then **Delete pipeline**. |
| 76 | + |
| 77 | +1. Select **Delete data pipeline** to confirm. |
| 78 | + |
| 79 | +Deleted data pipelines cannot be recovered. |
0 commit comments