Fix Elasticsearch connector configuration key mismatch#7607
Merged
yoshiokatsuneo merged 1 commit intogetredash:masterfrom Jan 24, 2026
Merged
Conversation
The Elasticsearch2 query runner was looking for configuration['server'] but BaseHTTPQueryRunner defines the schema field as 'url'. This caused a KeyError that manifested as 'Connection Test Failed: server'. Fixes getredash#7044
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
yoshiokatsuneo
approved these changes
Jan 24, 2026
Contributor
There was a problem hiding this comment.
Thank you for your contribution !
Actually, the issue looks being introduced by the PR . #6899 .
I confirmed that this PR fixed the issue by changing to use the correct "url" setting instead of wrong "server" setting.
woogakoki
added a commit
to wooga/redash
that referenced
this pull request
Feb 25, 2026
* master: (69 commits) Update Python version to 3.13 (getredash#7636) Update plotly.js to 3.3.1, react-pivottable to 0.11.0 (getredash#7634) Add charset option to RDS MySQL datasource (getredash#7616) Aggregate y value for same x (getredash#7631) fix(mysql): Change default charset to utf8mb4 (getredash#7615) Update packages for compatibility with setuptools 82 (getredash#7622) Snapshot: 26.02.0-dev chore: support ipv6 for server in docker (getredash#7596) Add impersonation option in trino datasource (getredash#7605) Fix Elasticsearch connector configuration key mismatch (getredash#7607) duckdb: Show catalog (database) where applicable (e.g. Motherduck) (getredash#7599) Snapshot: 26.01.0-dev Feature/catch notsupported exception (getredash#7573) Multi-org: format base path, not including protocol (getredash#7260) fix(destinations): Handle unicode characters in webhook notifications (getredash#7586) Persist updated values and apply saved dashboard parameters (getredash#7570) Add ibm-db package to enable DB2 as datasource: (getredash#7581) Snapshot: 25.12.0-dev PostgreSQL: allow connection parameters to be specified (getredash#7579) Add lineShape option for Line and Area charts (getredash#7582) ...
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
2 participants
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.
The Elasticsearch2 query runner was looking for configuration['server'] but BaseHTTPQueryRunner defines the schema field as 'url'. This caused a KeyError that manifested as 'Connection Test Failed: server'.
Fixes #7044
What type of PR is this?
Description
Fixed a configuration key mismatch in the Elasticsearch2 query runner that prevented successful connection testing.
Problem:
The
ElasticSearch2query runner inelasticsearch2.pywas attempting to accessself.configuration["server"], but theBaseHTTPQueryRunnerparent class defines this configuration field as"url"in its schema. This mismatch caused a KeyError when attempting to connect, which manifested to users as the error message:Connection Test Failed: 'server'.Solution:
Updated line 48 in
redash/query_runner/elasticsearch2.pyto use the correct configuration key:Before:
url = "{}{}".format(self.configuration["server"], url)
After:
url = "{}{}".format(self.configuration["url"], url)
This aligns the Elasticsearch connector implementation with the configuration schema defined in its parent class
BaseHTTPQueryRunner.Compatibility:
Tested with Elasticsearch 8.18.0. This fix applies to all Elasticsearch versions as it corrects the configuration schema alignment.
How is this tested?
Manual Testing Process:
make compose_build'server'error)Related Tickets & Documents
Fixes #7044
Mobile & Desktop Screenshots/Recordings (if there are UI changes)
N/A - This is a backend-only fix with no UI changes.