Skip to content

Commit 53c0f18

Browse files
committed
add table resync docs
1 parent 4453f28 commit 53c0f18

File tree

6 files changed

+66
-0
lines changed

6 files changed

+66
-0
lines changed

docs/integrations/data-ingestion/clickpipes/mongodb/add_table.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,3 +26,7 @@ This can be done by the following steps:
2626

2727
5. Click update.
2828
6. Upon successful update, the pipe will have statuses `Setup`, `Snapshot` and `Running` in that order. The table's initial load can be tracked in the **Tables** tab.
29+
30+
:::info
31+
CDC for existing tables resumes automatically after the new table’s snapshot completes.
32+
:::
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: 'Resyncing Specific Tables'
3+
description: 'Resyncing specific tables in a MongoDB ClickPipe'
4+
slug: /integrations/clickpipes/mongodb/table_resync
5+
sidebar_label: 'Resync Table'
6+
doc_type: 'guide'
7+
---
8+
9+
# Resyncing specific tables {#resync-tables}
10+
11+
There are scenarios where it would be useful to have specific tables of a pipe be re-synced. Some sample use-cases could be major schema changes on MongoDB, or maybe some data re-modelling on the ClickHouse.
12+
13+
While resyncing individual tables with a button click is a work-in-progress, this guide will share steps on how you can achieve this today in the MongoDB ClickPipe.
14+
15+
### 1. Remove the table from the pipe {#removing-table}
16+
17+
This can be followed by following the [table removal guide](./removing_tables).
18+
19+
### 2. Truncate or drop the table on ClickHouse {#truncate-drop-table}
20+
21+
This step is to avoid data duplication when we add this table again in the next step. You can do this by heading over to the **SQL Console** tab in ClickHouse Cloud and running a query.
22+
Note that we have validation to block table addition if the table already exists in ClickHouse and is not empty.
23+
24+
### 3. Add the table to the ClickPipe again {#add-table-again}
25+
26+
This can be followed by following the [table addition guide](./add_table).

docs/integrations/data-ingestion/clickpipes/mysql/add_table.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,3 +26,7 @@ This can be done by the following steps:
2626

2727
5. Click update.
2828
6. Upon successful update, the pipe will have statuses `Setup`, `Snapshot` and `Running` in that order. The table's initial load can be tracked in the **Tables** tab.
29+
30+
:::info
31+
CDC for existing tables resumes automatically after the new table’s snapshot completes.
32+
:::
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: 'Resyncing Specific Tables'
3+
description: 'Resyncing specific tables in a MySQL ClickPipe'
4+
slug: /integrations/clickpipes/mysql/table_resync
5+
sidebar_label: 'Resync Table'
6+
doc_type: 'guide'
7+
---
8+
9+
# Resyncing specific tables {#resync-tables}
10+
11+
There are scenarios where it would be useful to have specific tables of a pipe be re-synced. Some sample use-cases could be major schema changes on MySQL, or maybe some data re-modelling on the ClickHouse.
12+
13+
While resyncing individual tables with a button click is a work-in-progress, this guide will share steps on how you can achieve this today in the MySQL ClickPipe.
14+
15+
### 1. Remove the table from the pipe {#removing-table}
16+
17+
This can be followed by following the [table removal guide](./removing_tables).
18+
19+
### 2. Truncate or drop the table on ClickHouse {#truncate-drop-table}
20+
21+
This step is to avoid data duplication when we add this table again in the next step. You can do this by heading over to the **SQL Console** tab in ClickHouse Cloud and running a query.
22+
Note that we have validation to block table addition if the table already exists in ClickHouse and is not empty.
23+
24+
### 3. Add the table to the ClickPipe again {#add-table-again}
25+
26+
This can be followed by following the [table addition guide](./add_table).

docs/integrations/data-ingestion/clickpipes/postgres/add_table.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,3 +26,7 @@ This can be done by the following steps:
2626

2727
5. Click update.
2828
6. Upon successful update, the pipe will have statuses `Setup`, `Snapshot` and `Running` in that order. The table's initial load can be tracked in the **Tables** tab.
29+
30+
:::info
31+
CDC for existing tables resumes automatically after the new table’s snapshot completes.
32+
:::

sidebars.js

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -601,6 +601,7 @@ const sidebars = {
601601
"integrations/data-ingestion/clickpipes/mysql/add_table",
602602
"integrations/data-ingestion/clickpipes/mysql/pause_and_resume",
603603
"integrations/data-ingestion/clickpipes/mysql/remove_table",
604+
"integrations/data-ingestion/clickpipes/mysql/table_resync",
604605
"integrations/data-ingestion/clickpipes/mysql/resync",
605606
"integrations/data-ingestion/clickpipes/mysql/controlling_sync",
606607
],
@@ -637,6 +638,7 @@ const sidebars = {
637638
"integrations/data-ingestion/clickpipes/mongodb/add_table",
638639
"integrations/data-ingestion/clickpipes/mongodb/remove_table",
639640
"integrations/data-ingestion/clickpipes/mongodb/pause_and_resume",
641+
"integrations/data-ingestion/clickpipes/mongodb/table_resync",
640642
"integrations/data-ingestion/clickpipes/mongodb/resync",
641643
],
642644
},

0 commit comments

Comments
 (0)