Skip to content

fix: Correct Elasticsearch pagination docs — connector uses PIT + search_after#1712

Merged
lukekim merged 1 commit into
trunkfrom
fix/github-remove-nonfunctional-rate-params
May 12, 2026
Merged

fix: Correct Elasticsearch pagination docs — connector uses PIT + search_after#1712
lukekim merged 1 commit into
trunkfrom
fix/github-remove-nonfunctional-rate-params

Conversation

@claudespice
Copy link
Copy Markdown
Collaborator

@claudespice claudespice commented May 11, 2026

Summary

  • The Elasticsearch Limitations section incorrectly claims the connector issues a single _search request per query and is capped at 10,000 hits
  • The connector actually implements PIT (Point-In-Time) + search_after pagination for queries exceeding 10,000 rows or without a LIMIT clause

Changes

  • Updated the pagination limitation bullet to accurately describe the PIT-based pagination behavior

Reference

Verified against spiceai/spiceai at trunk — crates/data_components/src/elasticsearch/query_table.rs lines 230-231, 273-313

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 11, 2026

✅ 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: claudespice

@claudespice claudespice changed the title fix: Remove non-functional rate control params from GitHub connector docs fix: Correct Elasticsearch pagination docs — connector uses PIT + search_after May 11, 2026
@github-actions
Copy link
Copy Markdown

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

@lukekim lukekim merged commit a5d7893 into trunk May 12, 2026
8 of 10 checks passed
@lukekim lukekim deleted the fix/github-remove-nonfunctional-rate-params branch May 12, 2026 02:59
lukekim pushed a commit that referenced this pull request May 18, 2026
The deployment guide stated the connector issues a single `_search`
request per query returning at most 10,000 hits and advised users to
accelerate for larger result sets. In reality, the connector
automatically paginates using PIT + `search_after` for queries without
LIMIT or with LIMIT > 10,000 — matching what the connector index.md
already documents (corrected in PR #1712) and what the code implements
at query_table.rs:231.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants