Feat/elasticsearch connector#9
Merged
Grandvizir merged 13 commits intomainfrom Apr 8, 2026
Merged
Conversation
Supports API key, basic auth, and bearer token authentication. Uses search_after + PIT for efficient pagination with fallback to helpers.scan(). Configurable field mapping, optional query filter, and Elastic Cloud via cloud_id.
…ates Adds connection form fields for hosts, cloud_id, index, auth method, username, content/title field mapping, and TLS verification. Uses a yellow accent icon (Elasticsearch brand color).
35 tests covering: _parse_datetime utility, connector init/config parsing, client creation (API key, basic auth, bearer token, cloud_id, TLS), test_connection, fetch_document (content detection, fallback extraction, custom field mapping), list_documents (PIT pagination, empty index, scan fallback), and Django model integration. Uses sys.modules mocking to test lazy elasticsearch imports without requiring the package to be installed. Also fixes deprecated datetime.utcfromtimestamp() usage in the connector.
Update CHANGELOG, README, ingestion docs, configuration reference, and project structure to document the new Elasticsearch connector, its config keys, authentication methods, and pagination strategy.
Prevent test collection errors when third-party packages (openai, tiktoken, networkx, datasketch, sqlite-vec) are not installed by gracefully skipping affected test modules instead of erroring.
…to feat/elasticsearch-connector
Resolves migration conflict between 0003_add_elasticsearch_connector_type and 0003_add_encrypted_secret after merging main into the branch.
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
1 participant
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
Add an Elasticsearch connector to SCORE, allowing users to ingest documents from Elasticsearch indices alongside the
existing SharePoint, Confluence, and generic connectors.
Changes
basic auth, and bearer token authentication. Uses PIT (Point in Time) + search_after for memory-efficient pagination
with automatic fallback to helpers.scan() for older ES versions. Supports Elastic Cloud via cloud_id, configurable
field mapping (content, title, author, date), optional query DSL filter, and TLS verification settings.
connector type.
config panels (hosts, cloud_id, index, auth method, username, content/title field mapping, TLS verification) and a
yellow-accent Elasticsearch icon to the connector creation and listing pages.
score[elasticsearch]).
docs/project-structure.md): Documented the connector's config keys, authentication methods, pagination strategy, and
authority source weight (0.8).
connector init/config parsing, client creation for all auth methods, test_connection, fetch_document (content
detection, fallback extraction, custom field mapping), list_documents (PIT pagination, empty index, scan fallback),
and Django model integration. Uses sys.modules mocking to avoid requiring the elasticsearch package at test time.
Test Plan