spiceai
diff --git a/‎website/README.md‎
Lines changed: 10 additions & 10 deletions b/‎website/README.md‎
Lines changed: 10 additions & 10 deletions
diff --git a/‎website/docs/components/data-accelerators/cayenne.md‎
Lines changed: 5 additions & 5 deletions b/‎website/docs/components/data-accelerators/cayenne.md‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎website/docs/components/data-accelerators/index.md‎
Lines changed: 1 addition & 1 deletion b/‎website/docs/components/data-accelerators/index.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎website/docs/components/data-connectors/debezium.md‎
Lines changed: 19 additions & 1 deletion b/‎website/docs/components/data-connectors/debezium.md‎
Lines changed: 19 additions & 1 deletion
diff --git a/‎website/docs/components/data-connectors/dynamodb.md‎
Lines changed: 6 additions & 0 deletions b/‎website/docs/components/data-connectors/dynamodb.md‎
Lines changed: 6 additions & 0 deletions
diff --git a/‎website/docs/components/data-connectors/glue.md‎
Lines changed: 14 additions & 14 deletions b/‎website/docs/components/data-connectors/glue.md‎
Lines changed: 14 additions & 14 deletions
diff --git a/‎website/docs/components/data-connectors/kafka.md‎
Lines changed: 15 additions & 1 deletion b/‎website/docs/components/data-connectors/kafka.md‎
Lines changed: 15 additions & 1 deletion
@@ -40,21 +40,21 @@ The documentation supports multiple versions to maintain docs for different rele
 
 1. **Current docs** (`docs/`) — Working documentation from trunk, served at `/docs/trunk`
 2. **Versioned docs** — Auto-generated at build time from `release/<major>.<minor>` branches
-   - Highest version (e.g., v1.11.x) → "Next" (unreleased) at `/docs/next`
-   - Second highest (e.g., v1.10.x) → "Latest" (stable) at `/docs`
-   - Previous versions → at `/docs/v1.9`, etc.
+   - Highest version (e.g., v2.0.x) → "Next" (unreleased) at `/docs/next`
+   - Second highest (e.g., v1.11.x) → "Latest" (stable) at `/docs`
+   - Previous versions → at `/docs/v1.10`, etc.
 
 The version generation script ([scripts/generate-versions.sh](scripts/generate-versions.sh)) auto-detects release branches and uses `git archive` to extract docs from each without checking out the full repository.
 
 ### Creating a new version for a release
 
-When releasing a new version (e.g., v1.12):
+When releasing a new version (e.g., v2.1):
 
 1. **Create a release branch** for the new version:
 
    ```bash
-   git checkout -b release/1.12
-   git push origin release/1.12
+   git checkout -b release/2.1
+   git push origin release/2.1
    ```
 
 2. **That's it!** The build script auto-detects release branches matching the `release/<major>.<minor>` pattern. The next build will automatically include the new version.
@@ -71,17 +71,17 @@ When releasing a new version (e.g., v1.12):
 - `/docs` — Latest stable release (default)
 - `/docs/next` — Next release (unreleased, highest version branch)
 - `/docs/trunk` — Working docs from trunk
-- `/docs/v1.9` — Previous release versions
+- `/docs/v1.10` — Previous release versions
 
 ### Updating existing version docs
 
 To update docs for a released version, push changes directly to the corresponding release branch:
 
 ```bash
-git checkout release/1.12
+git checkout release/2.1
 # Make changes
-git commit -m "Update docs for v1.12.x"
-git push origin release/1.12
+git commit -m "Update docs for v2.1.x"
+git push origin release/2.1
 ```
 
 The next build will pick up the updated docs from the release branch.
@@ -11,8 +11,8 @@ tags:
   - s3-express
 ---
 
-:::info Alpha
-The Spice Cayenne Data Accelerator is in Alpha. Features and configuration may change. Available in Spice v1.9.0-rc.1 and later.
+:::info Beta
+The Spice Cayenne Data Accelerator is in Beta.
 :::
 
 Spice Cayenne is a data acceleration engine designed for high-performance, scalable query on large-scale datasets. Built on [Vortex](https://github.com/vortex-data/vortex), a next-generation columnar file format, Spice Cayenne combines columnar storage with in-process metadata management to provide fast query performance to scale to datasets beyond 1TB.
@@ -504,7 +504,7 @@ Query performance scales with available CPU cores. Vortex's columnar format supp
 
 Consider the following limitations when using Spice Cayenne acceleration:
 
-- **Alpha Status**: Spice Cayenne is in active development. Configuration options may change between releases.
+- **Beta Status**: Spice Cayenne is in active development. Configuration options may change between releases.
 - **File Mode Only**: Spice Cayenne only supports `mode: file` and does not support in-memory (`mode: memory`) acceleration.
 - **No Snapshot Support**: Spice Cayenne does not yet support [acceleration snapshots](../../features/data-acceleration/snapshots) for bootstrapping from object storage.
 - **S3 Express Only**: Standard S3 buckets are not supported for remote storage. Only S3 Express One Zone directory buckets are supported.
@@ -513,8 +513,8 @@ Consider the following limitations when using Spice Cayenne acceleration:
 - **No MVCC**: Multi-version concurrency control is not yet implemented. Snapshots and time-travel queries are planned for future releases.
 - **No File Compaction**: Automatic file compaction to reclaim space from deleted rows is not yet available.
 
-:::warning ALPHA SOFTWARE
-As an Alpha feature, Spice Cayenne should be thoroughly tested in development environments before production deployment. Monitor release notes for updates, breaking changes, and new capabilities.
+:::warning BETA SOFTWARE
+As a Beta feature, Spice Cayenne should be thoroughly tested in development environments before production deployment. Monitor release notes for updates, breaking changes, and new capabilities.
 :::
 
 ## Example Spicepod
 
@@ -30,7 +30,7 @@ By default, datasets are locally materialized using in-memory Arrow records.
 | Name       | Description                     | Status               | Engine Modes     |
 | ---------- | ------------------------------- | -------------------- | ---------------- |
 | `arrow`    | In-Memory Arrow Records         | Stable               | `memory`         |
-| `cayenne`  | [Spice Cayenne][cayenne]        | Alpha (v1.9.0-rc.1+) | `file`           |
+| `cayenne`  | [Spice Cayenne][cayenne]        | Beta                 | `file`           |
 | `duckdb`   | Embedded [DuckDB][duckdb]       | Stable               | `memory`, `file` |
 | `postgres` | Attached [PostgreSQL][postgres] | Release Candidate    | N/A              |
 | `sqlite`   | Embedded [SQLite][sqlite]       | Release Candidate    | `memory`, `file` |
 
@@ -35,6 +35,24 @@ datasets:
       mode: file # Persistence is recommended to not have to rebuild the table each time Spice starts.
 ```
 
+## Overview
+
+Upon startup, Spice subscribes to the specified Debezium-managed Kafka topic using either a uniquely generated consumer group or a custom one specified via `kafka_consumer_group_id`. If a persistent acceleration engine is used (with `mode: file`), data is fetched starting from the last processed record, allowing Spice to resume without reprocessing all historical change events.
+
+## Consumer Group Management
+
+The Debezium connector manages consumer groups to ensure data consistency across restarts. Offsets are committed to Kafka, allowing Spice to track consumption progress.
+
+**Default behavior:** When no `kafka_consumer_group_id` is specified, Spice automatically generates a unique consumer group ID and stores it in the acceleration metadata. On subsequent restarts, Spice retrieves and reuses this stored consumer group ID to maintain offset tracking and resume consumption from where it left off.
+
+**Custom consumer group:** If you specify a custom `kafka_consumer_group_id`, Spice stores this ID in the acceleration metadata. The same consumer group must be used on subsequent restarts. If no acceleration data exists and a custom consumer group is provided, Spice will reset its position to the oldest available offset and begin consuming from the start of the topic.
+
+**Consumer group mismatch error:** Spice will return an error if a restart is attempted with a different consumer group than what is stored in the acceleration metadata. This applies to both auto-generated and custom consumer group IDs. This safeguard prevents data inconsistency that could occur from mixing offsets between different consumer groups.
+
+To resolve a consumer group mismatch, either:
+- Use the same consumer group ID as stored in the acceleration
+- Reset the acceleration data to start fresh with a new consumer group
+
 ## Configuration
 
 ### `from`
@@ -79,7 +97,7 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 | `kafka_ssl_ca_location`                       | Path to the SSL/TLS CA certificate file for server verification.                                                                                                                                                                                                                                                                |
 | `kafka_enable_ssl_certificate_verification`   | Enable SSL/TLS certificate verification. Default: `true`.                                                                                                                                                                                                                                                                       |
 | `kafka_ssl_endpoint_identification_algorithm` | SSL/TLS endpoint identification algorithm. Default: `https`. Options: <ul><li>`none`</li><li>`https`</li></ul>                                                                                                                                                                                                                  |
-| `kafka_consumer_group_id`                     | Kafka consumer group id to use. If not set, a unique id will be generated.                                                                                                                                                                                                                                                      |
+| `kafka_consumer_group_id`                     | Kafka consumer group ID to use. If not set, a unique ID will be generated automatically. The consumer group ID (whether auto-generated or custom) is stored in the acceleration metadata and must remain consistent across restarts. See [Consumer Group Management](#consumer-group-management) for details.                   |
 
 ### `metrics`
 
 
@@ -680,6 +680,12 @@ datasets:
      - name: errors_transient_total
 ```
 
+:::warning[Limitations]
+
+- DynamoDB Streams connector does not support `refresh_sql`.
+
+:::
+
 ## Cookbooks
 
 - A cookbook recipe to configure DynamoDB as a data connector in Spice. [DynamoDB Data Connector](https://github.com/spiceai/cookbook/tree/trunk/dynamodb#readme)
 
@@ -50,13 +50,13 @@ The dataset name cannot be a [reserved keyword](../../reference/spicepod/keyword
 
 The following parameters are supported for configuring the connection to the Glue Data Catalog:
 
-| Parameter Name       | Definition                                                                  |
-| -------------------- | --------------------------------------------------------------------------- |
-| `glue_region`        | The AWS region for the Glue Data Catalog. E.g. `us-west-2`.                 |
+| Parameter Name       | Definition                                                                                                                                                                  |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `glue_region`        | The AWS region for the Glue Data Catalog. E.g. `us-west-2`.                                                                                                                 |
 | `glue_catalog_id`    | The Glue catalog ID. For Amazon S3 Tables, use the format `<account_id>:s3tablescatalog/<table_bucket_name>`. If not provided, the default catalog for the account is used. |
-| `glue_key`           | Access key (e.g. AWS_ACCESS_KEY_ID for AWS). If not provided, credentials will be loaded from environment variables or IAM roles.                                 |
-| `glue_secret`        | Secret key (e.g. AWS_SECRET_ACCESS_KEY for AWS). If not provided, credentials will be loaded from environment variables or IAM roles.                             |
-| `glue_session_token` | Session token (e.g. AWS_SESSION_TOKEN for AWS) for temporary credentials    |
+| `glue_key`           | Access key (e.g. AWS_ACCESS_KEY_ID for AWS). If not provided, credentials will be loaded from environment variables or IAM roles.                                           |
+| `glue_secret`        | Secret key (e.g. AWS_SECRET_ACCESS_KEY for AWS). If not provided, credentials will be loaded from environment variables or IAM roles.                                       |
+| `glue_session_token` | Session token (e.g. AWS_SESSION_TOKEN for AWS) for temporary credentials                                                                                                    |
 
 ## Examples
 
@@ -180,15 +180,15 @@ The IAM role or user needs the following permissions to access Iceberg tables in
 
 ### Permission Details
 
-| Permission | Purpose |
-|------------|---------|
-| `s3:ListBucket` | Required. Allows scanning all objects from the bucket |
-| `s3:GetObject` | Required. Allows fetching objects |
-| `glue:GetCatalog` | Required. Retrieve metadata about the specified catalog. |
+| Permission          | Purpose                                                        |
+| ------------------- | -------------------------------------------------------------- |
+| `s3:ListBucket`     | Required. Allows scanning all objects from the bucket          |
+| `s3:GetObject`      | Required. Allows fetching objects                              |
+| `glue:GetCatalog`   | Required. Retrieve metadata about the specified catalog.       |
 | `glue:GetDatabases` | Required. List the databases available in the current catalog. |
-| `glue:GetDatabase` | Required. Retrieve metadata about the specified database. |
-| `glue:GetTable` | Required. Retrieve metadata about the specified table. |
-| `glue:GetTables` | Required. List the tables available in the current database. |
+| `glue:GetDatabase`  | Required. Retrieve metadata about the specified database.      |
+| `glue:GetTable`     | Required. Retrieve metadata about the specified table.         |
+| `glue:GetTables`    | Required. List the tables available in the current database.   |
 
 ## Limitations
 
 
@@ -35,10 +35,24 @@ datasets:
 
 ## Overview
 
-Upon startup, Spice fetches all messages for the specified topic using a uniquely generated consumer group. If a persistent acceleration engine is used (with `mode: file`), data is fetched starting from the last processed record, allowing Spice to resume without reprocessing all historical data.
+Upon startup, Spice subscribes to the specified topic using either a uniquely generated consumer group or a custom one specified via `kafka_consumer_group_id`. If a persistent acceleration engine is used (with `mode: file`), data is fetched starting from the last processed record, allowing Spice to resume without reprocessing all historical data.
 
 Schema is automatically inferred from the first available topic message in JSON format. The connector creates the appropriate table schema for acceleration based on the detected data structure.
 
+## Consumer Group Management
+
+The Kafka connector manages consumer groups to ensure data consistency across restarts. Offsets are committed to Kafka, allowing Spice to track consumption progress.
+
+**Default behavior:** When no `kafka_consumer_group_id` is specified, Spice automatically generates a unique consumer group ID and stores it in the acceleration metadata. On subsequent restarts, Spice retrieves and reuses this stored consumer group ID to maintain offset tracking and resume consumption from where it left off.
+
+**Custom consumer group:** If you specify a custom `kafka_consumer_group_id`, Spice stores this ID in the acceleration metadata. The same consumer group must be used on subsequent restarts. If no acceleration data exists and a custom consumer group is provided, Spice will reset its position to the oldest available offset and begin consuming from the start of the topic.
+
+**Consumer group mismatch error:** Spice will return an error if a restart is attempted with a different consumer group than what is stored in the acceleration metadata. This applies to both auto-generated and custom consumer group IDs. This safeguard prevents data inconsistency that could occur from mixing offsets between different consumer groups.
+
+To resolve a consumer group mismatch, either:
+- Use the same consumer group ID as stored in the acceleration
+- Reset the acceleration data to start fresh with a new consumer group
+
 ## Configuration
 
 ### `from`