From fd65877b04e84de1ccb066f89a7db0b7d56daf21 Mon Sep 17 00:00:00 2001 From: claudespice Date: Thu, 10 Sep 2026 01:12:42 -0700 Subject: [PATCH] docs(ducklake): correct the embedded DuckDB version per release line Spice embeds DuckDB v1.4.4 on trunk (spiceai/spiceai#13742 downgraded it from 1.5.5 on 2026-08-30, shipping in v2.2.1). The DuckLake pages claimed 1.5.3. - vNext catalog page: 1.5.3 -> 1.4.4 (mirrors the connector page fixed in #2186) - version-2.2.x: v2.2.1 embeds 1.4.4, v2.2.0 embeds 1.5.5 - version-2.1.x: v2.1.2+ embeds 1.5.5, v2.1.0/v2.1.1 embed 1.5.3 - version-2.0.x left unchanged: v2.0.0/v2.0.1 really do embed 1.5.3 --- website/docs/components/catalogs/ducklake.md | 2 +- .../version-2.1.x/components/catalogs/ducklake.md | 2 +- .../version-2.1.x/components/data-connectors/ducklake.md | 2 +- .../version-2.2.x/components/catalogs/ducklake.md | 2 +- .../version-2.2.x/components/data-connectors/ducklake.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/components/catalogs/ducklake.md b/website/docs/components/catalogs/ducklake.md index 5d58b6c11..61473ca92 100644 --- a/website/docs/components/catalogs/ducklake.md +++ b/website/docs/components/catalogs/ducklake.md @@ -208,7 +208,7 @@ Spice integrates with multiple secret stores to help manage sensitive data secur :::warning[Limitations] -- Spice uses DuckDB 1.5.3, which supports DuckLake 1.0. Older DuckLake catalogs require a metadata migration before use — set `ducklake_automatic_migration: true` to perform it on attach (this rewrites catalog metadata and cannot be undone). See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). +- Spice embeds DuckDB **1.4.4** and supports the catalog schema required by its `ducklake` extension. For older catalogs, `ducklake_automatic_migration: true` performs an irreversible [metadata migration](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake) on attach. - The DuckLake DuckDB extension is downloaded at runtime on first use, requiring network connectivity. - The `information_schema` and `pg_catalog` system schemas are automatically filtered out during discovery. - Catalog refresh is non-incremental — a full re-query of `information_schema` is performed on each refresh cycle. diff --git a/website/versioned_docs/version-2.1.x/components/catalogs/ducklake.md b/website/versioned_docs/version-2.1.x/components/catalogs/ducklake.md index ec1820d00..b5a13a14f 100644 --- a/website/versioned_docs/version-2.1.x/components/catalogs/ducklake.md +++ b/website/versioned_docs/version-2.1.x/components/catalogs/ducklake.md @@ -198,7 +198,7 @@ Spice integrates with multiple secret stores to help manage sensitive data secur :::warning[Limitations] -- Spice uses DuckDB 1.5.3, which supports DuckLake 1.0. Older DuckLake catalogs require a metadata migration before use. See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). +- Spice v2.1.2 and later embed DuckDB 1.5.5; v2.1.0 and v2.1.1 embed DuckDB 1.5.3. Older DuckLake catalogs require a metadata migration before use. See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). - The DuckLake DuckDB extension is downloaded at runtime on first use, requiring network connectivity. - The `information_schema` and `pg_catalog` system schemas are automatically filtered out during discovery. - Catalog refresh is non-incremental — a full re-query of `information_schema` is performed on each refresh cycle. diff --git a/website/versioned_docs/version-2.1.x/components/data-connectors/ducklake.md b/website/versioned_docs/version-2.1.x/components/data-connectors/ducklake.md index 893255b16..bdea2a29c 100644 --- a/website/versioned_docs/version-2.1.x/components/data-connectors/ducklake.md +++ b/website/versioned_docs/version-2.1.x/components/data-connectors/ducklake.md @@ -201,7 +201,7 @@ datasets: :::warning[Limitations] -- Spice uses DuckDB 1.5.3, which supports DuckLake 1.0. Older DuckLake catalogs require a metadata migration before use. See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). +- Spice v2.1.2 and later embed DuckDB 1.5.5; v2.1.0 and v2.1.1 embed DuckDB 1.5.3. Older DuckLake catalogs require a metadata migration before use. See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). - The DuckLake DuckDB extension is downloaded at runtime on first use, requiring network connectivity. - The `ducklake_connection_string` parameter is required — unlike the catalog connector, it cannot be omitted. - Each dataset creates its own DuckDB connection pool. For querying many tables from the same catalog, consider using the [DuckLake Catalog Connector](../catalogs/ducklake) instead, which shares a single connection pool. diff --git a/website/versioned_docs/version-2.2.x/components/catalogs/ducklake.md b/website/versioned_docs/version-2.2.x/components/catalogs/ducklake.md index 6921948b4..2aad0c6b8 100644 --- a/website/versioned_docs/version-2.2.x/components/catalogs/ducklake.md +++ b/website/versioned_docs/version-2.2.x/components/catalogs/ducklake.md @@ -204,7 +204,7 @@ Spice integrates with multiple secret stores to help manage sensitive data secur :::warning[Limitations] -- Spice uses DuckDB 1.5.3, which supports DuckLake 1.0. Older DuckLake catalogs require a metadata migration before use — set `ducklake_automatic_migration: true` to perform it on attach (this rewrites catalog metadata and cannot be undone). See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). +- Spice v2.2.1 embeds DuckDB 1.4.4; v2.2.0 embeds DuckDB 1.5.5. Older DuckLake catalogs require a metadata migration before use — set `ducklake_automatic_migration: true` to perform it on attach (this rewrites catalog metadata and cannot be undone). See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). - The DuckLake DuckDB extension is downloaded at runtime on first use, requiring network connectivity. - The `information_schema` and `pg_catalog` system schemas are automatically filtered out during discovery. - Catalog refresh is non-incremental — a full re-query of `information_schema` is performed on each refresh cycle. diff --git a/website/versioned_docs/version-2.2.x/components/data-connectors/ducklake.md b/website/versioned_docs/version-2.2.x/components/data-connectors/ducklake.md index 7a550c8d3..a5e0f3586 100644 --- a/website/versioned_docs/version-2.2.x/components/data-connectors/ducklake.md +++ b/website/versioned_docs/version-2.2.x/components/data-connectors/ducklake.md @@ -203,7 +203,7 @@ datasets: :::warning[Limitations] -- Spice uses DuckDB 1.5.3, which supports DuckLake 1.0. Older DuckLake catalogs require a metadata migration before use — set `ducklake_automatic_migration: true` to perform it on attach (this rewrites catalog metadata and cannot be undone). See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). +- Spice v2.2.1 embeds DuckDB 1.4.4; v2.2.0 embeds DuckDB 1.5.5. Older DuckLake catalogs require a metadata migration before use — set `ducklake_automatic_migration: true` to perform it on attach (this rewrites catalog metadata and cannot be undone). See [DuckLake migration guide](https://ducklake.select/docs/stable/duckdb/guides/troubleshooting#connecting-to-an-older-ducklake). - The DuckLake DuckDB extension is downloaded at runtime on first use, requiring network connectivity. - The `ducklake_connection_string` parameter is required — unlike the catalog connector, it cannot be omitted. - Each dataset creates its own DuckDB connection pool. For querying many tables from the same catalog, consider using the [DuckLake Catalog Connector](../catalogs/ducklake) instead, which shares a single connection pool.