docs(cosmosdb): filters, projection and limits push down into Cosmos DB

[spiceemma]

Summary

spiceai/spiceai#14419 added filter, projection, and limit pushdown to the Cosmos DB connector. On vNext, the Cosmos DB reference page and deployment guide still listed "No filter / projection / limit pushdown" as a limitation. This PR replaces that bullet on both pages with a description of what pushes down: the projection and supported WHERE conditions when query is the default SELECT * FROM c, and a LIMIT with any query.

Source PRs

• fix(dynamodb, cosmosdb, mongodb): push filters down only where the source evaluates them as SQL does spiceai#14419 — fix(dynamodb, cosmosdb, mongodb): push filters down only where the source evaluates them as SQL does

Files changed (2)

• website/docs/components/data-connectors/cosmosdb/index.md
• website/docs/components/data-connectors/cosmosdb/deployment.md

Propagation: version-specific change, vNext only. git grep -c supports_filters_pushdown v2.3.2 -- crates/data-connectors/connector-cosmosdb returns no hits, so the "No filter / projection / limit pushdown" bullet stays correct in the 8 versioned copies (2.0.x–2.3.x, two pages each). grep -rln "No filter / projection / limit pushdown" website/docs now returns nothing.

The MongoDB and DynamoDB parts of #14419 change which filters push down, but no published page makes a claim about their pushdown, so neither page needs a change. grep -in push returns only an unrelated DynamoDB timestamp line.

Verification

All code is at origin/trunk b5126937a8. These are name/existence claims, each Reproduced by the quoted line:

• Pushdown only with the default query: crates/data-connectors/connector-cosmosdb/src/cosmosdb/provider.rs: fn pushes_down(&self) -> bool { self.config.query.trim().eq_ignore_ascii_case(super::DEFAULT_QUERY) }, with pub const DEFAULT_QUERY: &str = "SELECT * FROM c"; in cosmosdb/mod.rs. supports_filters_pushdown returns Unsupported for every filter when !self.pushes_down().
• Projection: pushed_down_query builds SELECT {projected properties} FROM c WHERE ….
• Inexact (Spice filters again): filter.rs classify: Some(_) => TableProviderFilterPushDown::Inexact, None => TableProviderFilterPushDown::Unsupported.
• Supported conditions, from Translator::translate: Operator::And; Operator::Or (both sides must translate); column-vs-literal Eq/NotEq/Lt/LtEq/Gt/GtEq; a boolean Expr::Column and Expr::Not over a boolean column only; IsNull; IsNotNull; Between { negated: false }; InList { negated: false } with values.len() > MAX_IN_VALUES (256) or any null refused; Like on a Kind::Utf8 column via like_prefix; DataFusion's own starts_with; _ => None.
• Limit: CosmosDBExec reads while read < limit for either query mode.

Behavior: Unverified, code inspection only. I did not run the claim that results match a query with no pushdown, because it needs a Cosmos DB account or the emulator. The source PR's differential round-trip suite (crates/runtime/tests/pushdown_roundtrip/) is the runtime evidence.

Dedupe: gh pr list --repo spiceai/docs --state all --search "spiceai/spiceai#14419" → []. Open bot PRs #2133, #2296, and #2297 do not touch these files.

Build: cd website && npm run build exits 0 and ends with [SUCCESS] Generated static files in "build".

Test plan

• cd website && npm run build passes
• Versioned-docs propagation checked: vNext only (no Cosmos DB pushdown at v2.3.2)
• Files updated: 2

Reproduction

Doc said (website/docs/components/data-connectors/cosmosdb/index.md:223 at 6409e742): No filter / projection / limit pushdown into Cosmos: SQL predicates are evaluated locally by DataFusion after the documents have been streamed in.
Code says (connector_cosmosdb::cosmosdb::provider::CosmosDBTableProvider::supports_filters_pushdown at trunk b5126937a8): let translator = Translator::new(&self.schema); Ok(filters.iter().map(|f| translator.classify(f)).collect())
Behavior claim: not run (needs a Cosmos DB account or the emulator), so the correction is Unverified, code inspection only for result equivalence.

[github-actions]

✅ Pull with Spice Passed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected
• ✅ Has at least one assignee: spiceemma

[github-actions]

🔍 Pull with Spice Failed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected

Failed checks:

• ❌ At least one assignee is required for this pull request.

Please address these issues and update your pull request.

[github-actions]

🔍 Pull with Spice Failed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected

Failed checks:

• ❌ At least one assignee is required for this pull request.

Please address these issues and update your pull request.

[Copilot]

Copilot review overview

🟡 Changes recommended

Both pages overstate filter support by omitting data-type and literal constraints.

Review effort: Balanced
Findings: 2

Open (2)

• Clarify filter pushdown limitations · New
• Clarify filter pushdown limitations · New

What changed in this PR

Updates vNext Cosmos DB documentation for pushdown behavior introduced by spiceai/spiceai#14419.

Changes:

• Documents projection and partial filter pushdown.
• Documents limit behavior and custom-query restrictions.

File	Description
cosmosdb/​index.md	Updates connector limitations.
cosmosdb/​deployment.md	Updates deployment limitations.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

🚀 deployed to https://a138b199.spiceai-org-website.pages.dev

[Copilot]

Copilot review overview

🟡 Changes recommended

Both pages overstate starts_with support and query-outcome equivalence.

Review effort: Balanced
Findings: 2

Open (2)

• Correct starts_with and pushdown guarantee claims · New
• Correct starts_with and pushdown guarantee claims · New

Resolved since last review (2)

• Clarify filter pushdown limitations
• Clarify filter pushdown limitations

[github-actions]

🚀 deployed to https://2142c9f8.spiceai-org-website.pages.dev

[Copilot]

Copilot review overview

🟡 Changes recommended

The documented filter constraints omit that floating-point literals must be finite.

Review effort: Balanced
Findings: 2

Open (2)

• Document Float64 finite-value requirement for filter pushdown · New
• Document Float64 finite-value requirement for filter pushdown · New

Resolved since last review (2)

• Correct starts_with and pushdown guarantee claims
• Correct starts_with and pushdown guarantee claims

[github-actions]

🚀 deployed to https://21b59e99.spiceai-org-website.pages.dev

[Copilot]

Copilot review overview

🟡 Changes recommended

Both pages inaccurately describe Boolean and BETWEEN pushdown support.

Review effort: Balanced
Findings: 2

Open (2)

• Clarify Boolean predicate and BETWEEN pushdown restrictions · New
• Clarify Boolean predicate and BETWEEN pushdown restrictions · New

Resolved since last review (2)

• Document Float64 finite-value requirement for filter pushdown
• Document Float64 finite-value requirement for filter pushdown

[github-actions]

🚀 deployed to https://ed5426fe.spiceai-org-website.pages.dev

[Copilot]

Copilot review overview

🟢 Approved

The documentation matches the referenced connector implementation and correctly remains limited to vNext.

Review effort: Balanced
Findings: None

Resolved since last review (2)

• Clarify Boolean predicate and BETWEEN pushdown restrictions
• Clarify Boolean predicate and BETWEEN pushdown restrictions

[github-actions]

🚀 deployed to https://cdbef61d.spiceai-org-website.pages.dev