fusion bulk edit documentation

Author: nayanj98

docs/core/architecture.mdx

@@ -5,12 +5,10 @@ sidebar_label: Architecture
 sidebar_position: 1
 ---
 
-# Architecture
+# OLake Go Architecture
 
 <!-- TODO: Ingestion architecture needs to be updated. -->
 
-## OLake Go Architecture
-
 For an in-depth look at OLake Go's architecture, including chunking strategies, concurrency models, and state management, explore our blog: [**A Deep Dive into OLake Go Architecture and Inner Workings**](/blog/olake-architecture-deep-dive).
 
 <div className="w-full lg:w-[80%] mx-auto">

docs/fusion/compaction/configuration.mdx

@@ -3,56 +3,62 @@ title: Configuration
 sidebar_position: 2
 ---
 
-# Configuring Table Compaction in Olake
+# Configuring Table Compaction
 
-Each table in Olake can have its **own compaction schedule and advanced settings**.
-Follow these steps to configure compaction for a specific table:
+Each table in OLake Fusion can have its **own compaction schedule and advanced settings**.
 
+## 1. Single Table Configuration
 
-### 1. Click the Configure Button
+### Step 1. Click the Configure Button
 
 Click the **Configure** button next to the table you want to compact.
 This opens a modal where you can schedule **Lite, Medium, and Full compactions**.
 
 ![Configure button](pathname:///img/docs/iceberg-maintenance/compaction/configure-button.webp)
 
 
-### 2. Set the Compaction Schedule
+### Step 2. Set the Compaction Schedule
 
 - Select a schedule from the **predefined dropdown options** or choose **Custom** to specify your own cron expression.
 - Compaction will run automatically according to the schedule set for that table.
 
 ![Compaction Schedule](pathname:///img/docs/iceberg-maintenance/compaction/configuration.webp)
 
-### 3. Advanced Config: Target File Size
+### Step 3. Advanced Config: Target File Size
 
 - Expand the **Advanced Config** panel in the modal.
 - Specify the **Target File Size** for the table (default **512 MB** if you leave it unchanged).
 
-For how **target file size** affects **Lite**, **Medium**, and **Full** compaction, see [Types of Compaction Supported in OLake](/docs/iceberg-maintenance/compaction/overview).
+For how **target file size** affects **Lite**, **Medium**, and **Full** compaction, see [Types of Compaction Supported in OLake Fusion](/docs/fusion/compaction/types-of-compaction/#types-of-compaction).
 
 > **Tip:** Choose a target size based on your query patterns and table size. Larger files can improve scan efficiency based on the query but may increase the cost of rewriting files.
 
 ![Target File Size](pathname:///img/docs/iceberg-maintenance/compaction/target-file-size.webp)
 
-### 4. Save the Configuration
+### Step 4. Save the Configuration
 
 - Click **Save**.
 
 ![Save Configuration](pathname:///img/docs/iceberg-maintenance/compaction/save-configuration.webp)
 
 - A dialog box confirms that the configuration was successful.
 
-![Save Configuration](pathname:///img/docs/iceberg-maintenance/compaction/configuration-successful.webp)
+![Save successful](/img/docs/iceberg-maintenance/compaction/configuration-successful.webp)
 
+- Once saved, the **Status** toggle for that table turns on automatically and compaction runs on the schedule you configured. Confirm this in the **Status** column as the toggle should appear active.
 
-### 5. Enable the Table for Compaction
+![status active](/img/docs/iceberg-maintenance/compaction/active-status-single.webp)
 
-- After saving, you will be redirected to the **Tables** page.
-- Locate the table and **toggle the Status switch** to activate scheduled compaction for that specific table.
+## 2. Bulk Configuration
 
-> **Important:** The **Status toggle must be switched on**. Even if a cron schedule is configured, compaction will not execute unless the table is enabled.
+Bulk configuration lets you apply the same compaction schedule and settings to multiple tables in one go, instead of configuring each table individually.
 
-![Enable compaction](pathname:///img/docs/iceberg-maintenance/compaction/enable-compaction.webp)
+To get started, select the tables you want to configure from the **Tables** page using their checkboxes, then click **Bulk Configure**. The same configuration modal opens — set the schedule, target file size, and save, exactly as described in Steps 2–4 of [Single Table Configuration](#1-single-table-configuration).
 
+![bulk select tables](/img/docs/iceberg-maintenance/compaction/bulk-select-tables.webp)
 
+:::note Default Configuration
+
+If any configuration is left unset, the following defaults apply: **24 hours** as the frequency for each compaction type and **512 MB** as the target file size.
+
+:::

docs/fusion/compaction/types-of-compaction.mdx

@@ -17,19 +17,21 @@ OLake supports three types of compaction:
 
 ### 1. Lite Compaction
 
-Lite compaction is the lightest and most frequently run type. It focuses on two things, **merging fragment into larger ones** and **converting Equality Delete Files into Position Delete Files**. Position Delete Files are cheaper for query engines to process, so this conversion alone improves read performance without doing a heavy rewrite. Since streaming writes and high-frequency CDC constantly produce small fragment files, Minor compaction is typically scheduled to run frequentlly to keep the table tidy before the clutter builds up.
+Lite compaction is the lightest and most frequently run type. It focuses on two things, **merging fragment into larger ones** and **converting Equality Delete Files into Position Delete Files**. Position Delete Files are cheaper for query engines to process, so this conversion alone improves read performance without doing a heavy rewrite. Since streaming writes and high-frequency CDC constantly produce small fragment files, Lite compaction is typically scheduled to run frequentlly to keep the table tidy before the clutter builds up.
 
 ### 2. Medium Compaction
 
-Medium compaction goes a step further. It **merges segment files up to the target file size**, and when too many Position Delete Files have accumulated, it merges them directly into the corresponding Data Files that is physically removing deleted rows from the table. This is more thorough than Minor compaction but still does not rewrite the entire table. The Medium Compaction is typically scheduled less frequently than the Lite Compaction to keep the table efficient and not spend too much compute.
+Medium compaction goes a step further. It **merges segment files up to the target file size**, and when too many Position Delete Files have accumulated, it merges them directly into the corresponding Data Files that is physically removing deleted rows from the table. This is more thorough than Lite compaction but still does not rewrite the entire table. The Medium Compaction is typically scheduled less frequently than the Lite Compaction to keep the table efficient and not spend too much compute.
 
 ### 3. Full Compaction
 
 Full compaction is the deepest and most comprehensive type. It rewrites all data files fragments, segments, and delete files into optimally sized files that exactly match the configured target file size. Because it rewrites the entire table, it is the most compute-intensive option and is typically run less frequently. Use it when tables have accumulated heavy fragmentation over time or when you need the best possible query performance.
 
 :::info Compaction precedence
 
-When more than one type of compaction is scheduled for a table to run at the same time, **only the highest runs**: **Full** overrides **Medium** and **Lite**; **Medium** overrides **Lite**. For example, if **Full**, **Medium**, and **Lite** are all due together, **Full** runs alone; if **Medium** and **Lite** are due together, **Medium** runs alone.
+When more than one type is scheduled at the same time, only the highest-priority type runs:
+
+**Full** > **Medium** > **Lite**
 
 :::
 

docs/fusion/core/architecture.mdx

@@ -3,9 +3,7 @@ title: Architecture
 sidebar_label: Architecture
 ---
 
-# Architecture
-
-## OLake Fusion Architecture
+# OLake Fusion Architecture
 
 <div className="w-full lg:w-[80%] mx-auto">
 ![OLake fusion architecture diagram](/img/docs/fusion-architecture.webp)

docs/fusion/getting-started/configure-first-compaction.mdx

@@ -132,18 +132,10 @@ After saving, a **Configuration Successful** modal appears. It **closes automati
 
 ![Configuration Successful modal](pathname:///img/docs/iceberg-maintenance/compaction/configuration-successful.webp)
 
-
-## Step 6: Enable Compaction
-
-Saving the configuration does not start compaction automatically. You must enable it:
-
-1. On the **Tables** page, locate the **Status** column next to the **Configure** button for your table.
-2. Use the **toggle** in the **Status** column to enable the compaction configuration.
+Once saved, the **Status** toggle for that table turns on automatically and compaction runs on the schedule you configured. Confirm this in the **Status** column as the toggle should appear active.
 
 ![Enable Configuration](pathname:///img/docs/iceberg-maintenance/compaction/enable-compaction.webp)
 
-Once enabled, OLake Fusion will start running compaction for that table according to the schedule you configured.
-
 ## Health Score and Last Run Status
 
 With a catalog and database selected, the **Tables** page shows one row per table. The sections below explain **Health Score** (overall table health) and **Last Run status** (per-type status for Lite, Medium, and Full compaction).

docs/fusion/getting-started/overview.mdx

@@ -34,7 +34,7 @@ You should consider running maintenance in the following scenarios:
 Iceberg Maintenance is available starting from v0.4.0. Upgrade OLake UI to access the **Maintenance** module.
 
 - **Existing users (Docker):** If you are already using OLake Go for Ingestion, follow the [upgrade guide](/docs/fusion/install/olake-ui/?setup-mode=configuration#updating-olake-ui-version) to access the Maintenance module.
-- **Existing users (Helm / Kubernetes):** If you are running OLake Go on Kubernetes, follow the [chart upgrade guide](http://localhost:3000/docs/fusion/install/kubernetes-compaction/?setup-mode=installation#upgrading-chart-version) to access the Maintenance module.
+- **Existing users (Helm / Kubernetes):** If you are running OLake Go on Kubernetes, follow the [chart upgrade guide](/docs/fusion/install/kubernetes-compaction/?setup-mode=installation#upgrading-chart-version) to access the Maintenance module.
 - **New Users (Docker):** Follow the [quickstart guide](/docs/fusion/install/olake-ui/?setup-mode=installation&quick-start=Ingestion+%2B+Maintenance#one-command-setup) to get started.
 - **New Users (Helm / Kubernetes):** Follow the [quickstart guide](/docs/fusion/install/kubernetes-compaction/?setup-mode=installation#quick-start) to get started.
 

docs/intro.mdx

@@ -99,7 +99,7 @@ import Head from '@docusaurus/Head'
     </a>
 </h1>
 
-<p align="center">Fastest open-source tool for replicating Databases to Apache Iceberg or Data Lakehouse. ⚡ Efficient, quick and scalable data ingestion for real-time analytics. Visit <a href="https://olake.io" target="_blank">olake.io</a> for the full documentation, and benchmarks</p>
+<p align="center">Fastest open-source tool for replicating Databases to Apache Iceberg or Data Lakehouse. ⚡ Efficient, quick and scalable data ingestion for real-time analytics.</p>
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';