mongo: add pause_and_resume + resync sections

Author: jgao54

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

@@ -0,0 +1,27 @@
+---
+title: 'Adding specific tables to a ClickPipe'
+description: 'Describes the steps need to add specific tables to a ClickPipe.'
+sidebar_label: 'Add Table'
+slug: /integrations/clickpipes/mongodb/add_table
+show_title: false
+---
+
+import Image from '@theme/IdealImage';
+import add_table from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/add_table.png'
+
+# Adding specific tables to a ClickPipe
+
+There are scenarios where it would be useful to add specific tables to a pipe. This becomes a common necessity as your transactional or analytical workload scales.
+
+## Steps to add specific tables to a ClickPipe {#add-tables-steps}
+
+This can be done by the following steps:
+1. [Pause](./pause_and_resume.md) the pipe.
+2. Click on Edit Table settings.
+3. Locate your table - this can be done by searching it in the search bar.
+4. Select the table by clicking on the checkbox.
+<br/>
+<Image img={add_table} border size="md"/>
+
+5. Click update.
+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.

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

@@ -0,0 +1,46 @@
+---
+title: 'Pausing and Resuming a MongoDB ClickPipe'
+description: 'Pausing and Resuming a MongoDB ClickPipe'
+sidebar_label: 'Pause Table'
+slug: /integrations/clickpipes/mongodb/pause_and_resume
+---
+
+import Image from '@theme/IdealImage';
+import pause_button from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/pause_button.png'
+import pause_dialog from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/pause_dialog.png'
+import pause_status from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/pause_status.png'
+import resume_button from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resume_button.png'
+import resume_dialog from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resume_dialog.png'
+
+There are scenarios where it would be useful to pause a MongoDB ClickPipe. For example, you may want to run some analytics on existing data in a static state. Or, you might be performing upgrades on MongoDB. Here is how you can pause and resume a MongoDB ClickPipe.
+
+## Steps to pause a MongoDB ClickPipe {#pause-clickpipe-steps}
+
+1. In the Data Sources tab, click on the MongoDB ClickPipe you wish to pause.
+2. Head over to the **Settings** tab.
+3. Click on the **Pause** button.
+
+<Image img={pause_button} border size="md"/>
+
+4. A dialog box should appear for confirmation. Click on Pause again.
+
+<Image img={pause_dialog} border size="md"/>
+
+4. Head over to the **Metrics** tab.
+5. In around 5 seconds (and also on page refresh), the status of the pipe should be **Paused**.
+
+<Image img={pause_status} border size="md"/>
+
+## Steps to resume a MongoDB ClickPipe {#resume-clickpipe-steps}
+1. In the Data Sources tab, click on the MongoDB ClickPipe you wish to resume. The status of the mirror should be **Paused** initially.
+2. Head over to the **Settings** tab.
+3. Click on the **Resume** button.
+
+<Image img={resume_button} border size="md"/>
+
+4. A dialog box should appear for confirmation. Click on Resume again.
+
+<Image img={resume_dialog} border size="md"/>
+
+5. Head over to the **Metrics** tab.
+6. In around 5 seconds (and also on page refresh), the status of the pipe should be **Running**.

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

@@ -0,0 +1,26 @@
+---
+title: 'Removing specific tables from a ClickPipe'
+description: 'Removing specific tables from a ClickPipe'
+sidebar_label: 'Remove Table'
+slug: /integrations/clickpipes/mongodb/removing_tables
+---
+
+import Image from '@theme/IdealImage';
+import remove_table from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/remove_table.png'
+
+In some cases, it makes sense to exclude specific tables from a MongoDB ClickPipe - for example, if a table isn't needed for your analytics workload, skipping it can reduce storage and replication costs in ClickHouse.
+
+## Steps to remove specific tables {#remove-tables-steps}
+
+The first step is to remove the table from the pipe. This can be done by the following steps:
+
+1. [Pause](./pause_and_resume.md) the pipe.
+2. Click on Edit Table Settings.
+3. Locate your table - this can be done by searching it in the search bar.
+4. Deselect the table by clicking on the selected checkbox.
+<br/>
+
+<Image img={remove_table} border size="md"/>
+
+5. Click update.
+6. Upon successful update, in the **Metrics** tab the status will be **Running**. This table will no longer be replicated by this ClickPipe.

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

@@ -0,0 +1,45 @@
+---
+title: 'Resyncing a Database ClickPipe'
+description: 'Doc for resyncing a database ClickPipe'
+slug: /integrations/clickpipes/mongodb/resync
+sidebar_label: 'Resync ClickPipe'
+---
+
+import resync_button from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resync_button.png'
+import Image from '@theme/IdealImage';
+
+### What does Resync do? {#what-mongodb-resync-do}
+
+Resync involves the following operations in order:
+
+1. The existing ClickPipe is dropped, and a new "resync" ClickPipe is kicked off. Thus, changes to source table structures will be picked up when you resync.
+2. The resync ClickPipe creates (or replaces) a new set of destination tables which have the same names as the original tables except with a `_resync` suffix.
+3. Initial load is performed on the `_resync` tables.
+4. The `_resync` tables are then swapped with the original tables. Soft deleted rows are transferred from the original tables to the `_resync` tables before the swap.
+
+All the settings of the original ClickPipe are retained in the resync ClickPipe. The statistics of the original ClickPipe are cleared in the UI.
+
+### Use cases for resyncing a ClickPipe {#use-cases-mongodb-resync}
+
+Here are a few scenarios:
+
+1. You may need to perform major schema changes on the source tables which would break the existing ClickPipe and you would need to restart. You can just click Resync after performing the changes.
+2. Specifically for Clickhouse, maybe you needed to change the ORDER BY keys on the target tables. You can Resync to re-populate data into the new table with the right sorting key.
+
+:::note
+You can resync multiple times, however please account for the load on the source database when you resync,
+since initial load with parallel threads is involved each time.
+:::
+
+### Resync ClickPipe Guide {#guide-mongodb-resync}
+
+1. In the Data Sources tab, click on the MongoDB ClickPipe you wish to resync.
+2. Head over to the **Settings** tab.
+3. Click on the **Resync** button.
+
+<Image img={resync_button} border size="md"/>
+
+4. A dialog box should appear for confirmation. Click on Resync again.
+5. Head over to the **Metrics** tab.
+6. In around 5 seconds (and also on page refresh), the status of the pipe should be **Setup** or **Snapshot**.
+7. The initial load of the resync can be monitored in the **Tables** tab - in the **Initial Load Stats** section.

sidebars.js

@@ -809,6 +809,16 @@ const sidebars = {
           items: [
             "integrations/data-ingestion/clickpipes/mongodb/index",
             "integrations/data-ingestion/clickpipes/mongodb/datatypes",
+            {
+              type: "category",
+              label: "Operations",
+              items: [
+                "integrations/data-ingestion/clickpipes/mongodb/add_table",
+                "integrations/data-ingestion/clickpipes/mongodb/remove_table",
+                "integrations/data-ingestion/clickpipes/mongodb/pause_and_resume",
+                "integrations/data-ingestion/clickpipes/mongodb/resync",
+              ],
+            },
             {
               type: "category",
               label: "Source",