---

date: 2025-03-17 title: 'Spice v1.0.6 (Mar 17, 2025)' type: blog authors: [sgrebnov] tags: [release, duckdb, iceberg, awsglue, acceleration]

Announcing the release of Spice v1.0.6 ⚡

Spice v1.0.6 improves stability for DuckDB acceleration, Iceberg Data/Catalog connector improvements when using AWS Glue, and fixes an issue with the ready_state: on_registration federation fallback when using DuckDB. In addition, redundant data refreshes on startup are avoided for accelerations with persistent data.

Highlights in v1.0.6

• Iceberg Data/Catalog Connector Improvements: Improves Iceberg data & catalog connector reliability, including bug fixes for AWS Glue API rate-limiting and compatibility, REST API pagination support, explicit AWS credential handling, and support for AWS STS role assumption.

• Fixes On-Registration Fallback when using DuckDB: Previously, when using DuckDB as a data accelerator and the ready_state: on_registration configuration, queries made during the initial data refresh did not properly fallback to the federated source. This is now fixed.

• DuckDB downgraded for Stability: DuckDB has been downgraded to v1.1.3 due to a regression in memory handling tracked by duckdb/duckdb issue #16640. Once resolved and validated, Spice will re-upgrade to v1.2.x.

• Expanded Integration Tests: Additional integration tests covering federated accelerator behavior and graceful shutdown processes have been added.

• Optimized Data Refresh for Persistent Accelerations: Changed behavior in v1.0.6. When using persistent (file-mode) acceleration without a defined refresh interval, Spice performs a full refresh at startup only if no previously accelerated data is available. This ensures efficient startup behavior by avoiding unnecessary refreshes. This logic applies only to full refreshes when no refresh interval is specified.

To maintain the previous behavior and always refresh on every startup, set:

Contributors

• @peasee
• @phillipleblanc
• @sgrebnov
• @lukekim
• @Sevenannn

Breaking Changes

Starting from v1.0.6 when using persistent (file-mode) acceleration without a defined refresh interval, Spice performs a full refresh at startup only if no previously accelerated data is available. To maintain the previous behavior and always refresh on every startup, set:

Cookbook Updates

No new recipes.

Upgrading

To upgrade to v1.0.6, use one of the following methods:

CLI:

Homebrew:

Docker:

Pull the spiceai/spiceai:1.0.6 image:

For available tags, see DockerHub.

Helm:

What's Changed

Dependencies

• duckdb-rs: Downgraded from 1.2.0 to 1.1.3

Changelog

• Implement proper ready_state: on_registration for federation enabled accelerators by @phillipleblanc in #5019
• Add indexes and primary keys mismatch detection for DuckDB Acceleration by @sgrebnov in #5045
• Add comprehensive integration tests for the ready_state behavior by @phillipleblanc in #5042
• Add test Spicepod for acceleration with constraints by @sgrebnov in #4891
• Add test Spicepod for DuckDB append acceleration with constraints by @sgrebnov in #4898
• Add DuckDB graceful shutdown test to E2E CI tests by @sgrebnov in #5047
• Update duckdb_append_with_pk_and_indexes.yaml (work for duckdb 1.1.x) by @sgrebnov in #5067
• fix: Downgrade to DuckDB 1.1.3 by @peasee in #5055
• fix: Acceleration federation integration test by @peasee in #5070
• Improvements to Iceberg Catalog/Data Connector by @phillipleblanc in #5071
• Add Results-Cache-Status to indicate query result came from cache by @phillipleblanc in #4809
• fix: Spice.ai schema inference by @peasee in #4674
• Add refresh_on_startup Spicepod configuration param by @phillipleblanc and @sgrebnov in #5086
• Test restart behavior of DuckDB file acceleration against glue iceberg table by @Sevenannn #5075
• Run Iceberg Data Connector - DuckDB File mode integration test by @Sevenannn #5069
• Integration test for glue iceberg catalog by @Sevenannn #5077

Full Changelog: https://github.com/spiceai/spiceai/compare/v1.0.5...v1.0.6