Repository navigation
docs: SQL and search depth limits, Flight SQL prepared statement handles, Iceberg vended storage hosts, Bedrock reasoning_content, refused GGUF architectures - #2441
Merged
Conversation
…les, Iceberg vended storage hosts, Bedrock reasoning_content, refused GGUF architectures
Contributor
✅ Pull with Spice PassedPassing checks:
|
Contributor
🔍 Pull with Spice FailedPassing checks:
Failed checks:
Please address these issues and update your pull request. |
Contributor
There was a problem hiding this comment.
🟢 Approved
No active review issues block the documentation-only updates to vNext runtime guidance.
No open issues 🎉
What changed in this PR
This documentation-only PR updates vNext guidance for five runtime changes merged into spiceai/spiceai. The version 2.4.x documentation remains unchanged because these changes postdate v2.4.0.
Changes:
- Documents SQL and search expression-depth limits and process-specific Flight SQL prepared statement handles.
- Updates Iceberg storage-host validation behavior and refusal errors.
- Clarifies Bedrock reasoning response fields and load-time rejection of unsupported GGUF architectures.
| File | Description |
|---|---|
website/docs/reference/sql/operators.md |
Documents the depth-limit error for selected, grouped, ordered, and VALUES expressions. |
website/docs/features/search/vector-search.md |
Documents the where nesting limit and HTTP 400 response. |
website/docs/components/models/index.md |
Clarifies load-time rejection of encoder-decoder and diffusion GGUFs. |
website/docs/components/models/bedrock.md |
Corrects non-streamed reasoning fields and links the streaming issue. |
website/docs/components/data-connectors/iceberg.md |
Explains connection-time host validation and removes the obsolete file:// restriction. |
website/docs/api/arrow-flight-sql/index.md |
Documents prepared statement handle validity across restarts and replicas. |
Review effort: Balanced
Contributor
|
🚀 deployed to https://5be9a493.spiceai-org-website.pages.dev |
lukekim
approved these changes
Oct 27, 2026
This was referenced Oct 28, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR documents five changes merged to
spiceai/spiceaitrunk, in vNext (website/docs/) only. None of the merge commits is an ancestor ofv2.4.0(git merge-base --is-ancestor <sha> v2.4.0fails for all five), so theversion-2.4.xsnapshot correctly documents the earlier behavior.reference/sql/operators,features/search/vector-search): a selected, grouped, or ordered expression, or aVALUEScell, nested more than 512 levels deep fails with its own message. A/v1/searchwherecondition nested more than 512 levels deep is rejected with HTTP400.api/arrow-flight-sql): a handle is valid only on the process that issued it. After a restart, or on another replica, the call fails withInvalidArgument. The runtime's error links to this page, which did not explain it.components/data-connectors/iceberg): a host name is now resolved when Spice connects, and Spice connects only to the addresses it checked. The new refusal error is documented. Thefile://sentence is removed because the guard was deleted.reasoning_content(components/models/bedrock): a non-streamed reply now returns the reasoning text inreasoning_content, not incontent, and omits redacted reasoning. The link now points at the open streaming enhancement, Enhancement: Streamed chat completions carry the model's reasoning (delta.reasoning_content) spiceai#15595, because #15406 is closed.components/models).Source PRs
Verification
The values below were read on
spiceai/spiceaiorigin/trunkat814e639e8eb55eacbe3f3fadaad2ec0aaf712c05. Statements about behavior come from reading the code (Unverified, code inspection only), except where a source PR records its own run. The runtime was not run for this docs PR.The source PRs ran their own reproductions. spiceai/spiceai#15430 ran an E2E against
spicedbuilt from trunk and from the branch. With the fix, the query fails withdirects storage requests to a host that is not allowed, and the internal listener received no requests.Later revert, removal, or retune: searching merged spiceai/spiceai PRs for
MAX_UNPROTECTED_EXPR_DEPTH,prepared_statement_handle,vended_transport,ResponseBlock::Reasoning, andis_diffusionreturned only the source PRs.Known limitations, each stated on the page: a handle cannot be reused after a restart or on another replica (the "Breaking Changes" section of spiceai/spiceai#15347). Streamed Bedrock replies still carry no reasoning text (spiceai/spiceai#15595, open).
Merge-commit ancestry:
Files changed (6):
Build:
NODE_OPTIONS=--max-old-space-size=12288 npm run build(inwebsite/):The style grep (
docs-pr-hygiene.md§"Local Docusaurus build gate") over the added lines found nothing. The new link../../reference/sql/operators.md#logical-operatorsresolves to## Logical Operatorsatoperators.md:348.Test plan
cd website && npm run buildpasses (output above)Review gate
codexnot installed (receipt:attempt=codex result=not-installed,engine=none)/security-review: not run — docs-only Markdown diff; the same review on the sibling docs-only PR docs: request-context metric labels, HTTPS redirect guard, ORC metadata limit, scalar function memory, OTLP log record size #2440 found nothing/simplify: not run — docs-only diff, no code