date: 2026-02-10 title: 'Spice v1.11.1 (Feb 10, 2026)' type: blog authors: [jeadie] tags: [release, cayenne, data-connector, dynamodb, flightsql]
Announcing the release of Spice v1.11.1! 🛠️
v1.11.1 is a patch release improving Spice Cayenne (opens in a new tab) accelerator reliability and performance, enhancing DynamoDB Streams and HTTP data connectors, and fixing issues in Federated Task History and FlightSQL.
This release includes stability and performance fixes for the Spice Cayenne (opens in a new tab) accelerator:
RoaringBitmap. Deletion scans now use Vortex-native streaming with filter pushdown and project only row indices, achieving zero data I/O for delete operations.constraints and on_conflict configurations are now automatically inferred from federated table metadata, enabling datasets like DynamoDB (opens in a new tab) to work without explicitly defining primary_key in the Spicepod.DELETE operations on partitioned Cayenne tables failed.lag_exceeds_shard_retention_behavior parameter with values error (default), ready_before_load, or ready_after_load.response_status column (UInt16). 4xx responses (e.g., 404 Not Found) are treated as valid queryable data and cached normally. 5xx responses are retried with backoff, returned to the user, but excluded from the cache to prevent transient server errors from polluting cached results.SnapshotManager operations and general snapshot reliability improvements.Schema error: project index out of bounds errors in cluster mode.No breaking changes.
No major cookbook updates. The Spice Cookbook (opens in a new tab) includes 86 recipes to help you get started with Spice quickly and easily.
To upgrade to v1.11.1, use one of the following methods:
CLI:
Homebrew:
Docker:
Pull the spiceai/spiceai:1.11.1 image:
For available tags, see DockerHub (opens in a new tab).
Helm:
AWS Marketplace:
Spice is available in the AWS Marketplace (opens in a new tab).
constraints/on_conflict in Cayenne Acceleration by @krinart (opens in a new tab) in #9335 (opens in a new tab)SchemaCastScanExec before applying changes in process_upsert_batch by @krinart (opens in a new tab) in #9297 (opens in a new tab)