You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "serverdevil (via GitHub)" <gi...@apache.org> on 2025/07/07 08:07:56 UTC
[D] Superset + Opensearch integration [superset]
GitHub user serverdevil created a discussion: Superset + Opensearch integration
Superset + Opensearch setup using elasticsearch-dbapi library for interfacing with opensearch. the Elasticsearch (opendistro and sql) options are available in the data connection menu. Test connection works fine. I'm using the following url
`odelasticsearch+http://<username>:<password>@opensearch:9200/?v2=1&sql_path=_plugins/_sql`
When I try to create a dataset, upon selecting a table e.g. `logs` I get the following error.
I have read the discussions around SQL lab autogenerating queries with backticks which can be remedied by making them single quotes, but this is an internal query that I can't influence. Does anybody have a resolution for this?
Checked out the `sqlglot` library code too but no luck. In Superset the `Dialect` switch case has `odelasticsearch` commented out. What does it mean for the Dialect? What default is assumed?
```superset | 2025-07-07 06:22:33,319:WARNING:superset.views.error_handling:SupersetErrorException
superset | Traceback (most recent call last):
superset | File "/app/.venv/lib/python3.10/site-packages/superset/sql/parse.py", line 267, in _parse
superset | return sqlglot.parse(script, dialect=dialect)
superset | File "/app/.venv/lib/python3.10/site-packages/sqlglot/__init__.py", line 102, in parse
superset | return Dialect.get_or_raise(read or dialect).parse(sql, **opts)
superset | File "/app/.venv/lib/python3.10/site-packages/sqlglot/dialects/dialect.py", line 991, in parse
superset | return self.parser(**opts).parse(self.tokenize(sql), sql)
superset | File "/app/.venv/lib/python3.10/site-packages/sqlglot/parser.py", line 1507, in parse
superset | return self._parse(
superset | File "/app/.venv/lib/python3.10/site-packages/sqlglot/parser.py", line 1579, in _parse
superset | self.raise_error("Invalid expression / Unexpected token")
superset | File "/app/.venv/lib/python3.10/site-packages/sqlglot/parser.py", line 1620, in raise_error
superset | raise error
superset | sqlglot.errors.ParseError: Invalid expression / Unexpected token. Line 2, Col: 14.
superset | SELECT *
superset | FROM `default`.logs
superset | LIMIT 100
superset |
superset | The above exception was the direct cause of the following exception:
superset |
superset | Traceback (most recent call last):
superset | File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
superset | rv = self.dispatch_request()
superset | File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
superset | return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
superset | File "/app/.venv/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 109, in wraps
superset | return f(self, *args, **kwargs)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/views/base_api.py", line 120, in wraps
superset | duration, response = time_function(f, self, *args, **kwargs)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/utils/core.py", line 1369, in time_function
superset | response = func(*args, **kwargs)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/utils/log.py", line 304, in wrapper
superset | value = f(*args, **kwargs)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/databases/api.py", line 1013, in table_metadata
superset | payload = database.db_engine_spec.get_table_metadata(database, table)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/db_engine_specs/base.py", line 1087, in get_table_metadata
superset | return get_table_metadata(database, table)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/databases/utils.py", line 100, in get_table_metadata
superset | "selectStar": database.select_star(
superset | File "/app/.venv/lib/python3.10/site-packages/superset/models/core.py", line 771, in select_star
superset | return self.db_engine_spec.select_star(
superset | File "/app/.venv/lib/python3.10/site-packages/superset/db_engine_specs/base.py", line 1706, in select_star
superset | sql = SQLScript(sql, engine=cls.engine).format()
superset | File "/app/.venv/lib/python3.10/site-packages/superset/sql/parse.py", line 670, in __init__
superset | self.statements = statement_class.split_script(script, engine)
superset | File "/app/.venv/lib/python3.10/site-packages/superset/sql/parse.py", line 327, in split_script
superset | ast = cls._parse(remainder, engine)[0]
superset | File "/app/.venv/lib/python3.10/site-packages/superset/sql/parse.py", line 270, in _parse
superset | raise SupersetParseError(
superset | superset.exceptions.SupersetParseError: Error parsing near '`' at line 2:14```
```
GitHub link: https://github.com/apache/superset/discussions/34083
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Superset + Opensearch integration
<!-- Answer -->
The `'odelasticsearch'` dialect is commented out in Superset's dialect mapping, so Superset defaults to a generic SQL dialect for query parsing and generation. This fallback uses backticks for quoting identifiers (e.g., `FROM \`default\`.logs`), which Opensearch SQL does not support, leading to parsing errors when creating datasets or running internal queries [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py).
Currently, there is no built-in workaround in Superset for this issue. The `SQL_QUERY_MUTATOR` config can alter outgoing queries, but it does not reliably affect internal queries like those used for dataset metadata [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py). Superset does allow for extending SQL dialects via `SQLGLOT_DIALECTS_EXTENSIONS`, but this only works if the dialect is referenced in the code, which is not the case for `'odelasticsearch'` right now.
To resolve this long-term, a new or updated dialect for Opensearch would need to be contributed to Superset, either by implementing a custom engine spec/plugin or by submitting a pull request to add proper dialect support [[source]](https://github.com/apache/superset/discussions/31619). Until then, the backtick quoting issue will persist for internal queries with Opensearch connections.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=hallucination) | [Report đ](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/18231ef1-9d1e-4079-8566-03509107eb1a?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34083)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13680873
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Superset + Opensearch integration
<!-- Answer -->
To add Opensearch dialect support in Superset, youâll need to:
1. Implement or extend an EngineSpec subclass for Opensearch in `superset/db_engine_specs/`. Use classes like `PrestoEngineSpec` or `PostgresEngineSpec` as templatesâdefine engine name, aliases, driver mappings, column type mappings, and SQL generation logic. Pay special attention to identifier quoting and SQL syntax that Opensearch expects [[example](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/postgres.py)].
2. Ensure there is a corresponding sqlglot dialect for Opensearch. If one doesnât exist, you may need to contribute it upstream to sqlglot or implement it locally. This is crucial for correct SQL parsing and formatting, especially for identifier quoting (avoid backticks, use double quotes or none as required by Opensearch) [[reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py)].
3. Register the new dialect in the `SQLGLOT_DIALECTS` mapping so Superset uses it for parsing and formatting queries for Opensearch connections. If you need to extend or override dialect behavior, use the `SQLGLOT_DIALECTS_EXTENSIONS` config [[reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py)].
4. If you want to distribute the dialect as a plugin, use Supersetâs plugin architecture based on Python entry points. This allows you to install new EngineSpecs without modifying the core codebase [[reference](https://github.com/apache/superset/issues/31932)].
5. Add unit and integration tests for your EngineSpec, covering query parsing, dataset creation, and error handling. Manually verify that the UI works as expected with Opensearch.
6. Update documentation for users and contributors, including connection instructions, limitations, and any custom configuration.
If Opensearch support is missing in SQLAlchemy or sqlglot, you may need to contribute dialects upstream or adapt existing ones. For more on contributing, see Supersetâs [contribution guidelines](https://superset.apache.org/docs/contributing/contribution-guidelines).
Let me know if you want pointers to specific code examples or have questions about any of these steps.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=hallucination) | [Report đ](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/78a1f4d3-1867-4594-9423-2060ad9a5539?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34083)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13681016
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "serverdevil (via GitHub)" <gi...@apache.org>.
GitHub user serverdevil added a comment to the discussion: Superset + Opensearch integration
@dosu Can you outline detailed contributions required to support a new dialect for `opensearch` in superset?
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13680996
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Superset + Opensearch integration
<!-- Answer -->
To add Opensearch dialect support in Superset, youâll need to:
1. Implement or extend an EngineSpec subclass for Opensearch in `superset/db_engine_specs/`. Use classes like `PrestoEngineSpec` or `PostgresEngineSpec` as templatesâdefine engine name, aliases, driver mappings, column type mappings, and SQL generation logic. Pay special attention to identifier quoting and SQL syntax that Opensearch expects [[example](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/postgres.py)].
2. Ensure there is a corresponding sqlglot dialect for Opensearch. If one doesnât exist, you may need to contribute it upstream to sqlglot or implement it locally. This is crucial for correct SQL parsing and formatting, especially for identifier quoting (avoid backticks, use double quotes or none as required by Opensearch) [[reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py)].
3. Register the new dialect in the `SQLGLOT_DIALECTS` mapping so Superset uses it for parsing and formatting queries for Opensearch connections. If you need to extend or override dialect behavior, use the `SQLGLOT_DIALECTS_EXTENSIONS` config [[reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py)].
4. If you want to distribute the dialect as a plugin, use Supersetâs plugin architecture based on Python entry points. This allows you to install new EngineSpecs without modifying the core codebase [[reference](https://github.com/apache/superset/issues/31932)].
5. Add unit and integration tests for your EngineSpec, covering query parsing, dataset creation, and error handling. Manually verify that the UI works as expected with Opensearch.
6. Update documentation for users and contributors, including connection instructions, limitations, and any custom configuration.
If Opensearch support is missing in SQLAlchemy or sqlglot, you may need to contribute dialects upstream or adapt existing ones. For more on contributing, see Supersetâs [contribution guidelines](https://superset.apache.org/docs/contributing/contribution-guidelines).
Let me know if you want pointers to specific code examples or have questions about any of these steps.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=78a1f4d3-1867-4594-9423-2060ad9a5539) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13681016
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "serverdevil (via GitHub)" <gi...@apache.org>.
GitHub user serverdevil added a comment to the discussion: Superset + Opensearch integration
I tried implementing a bare minimum dialect but any custom stuff that I try to do and build a docker image with `--target` `dev`, the database connection modal's "Connect" button never gets enabled.
I even reverted all my changes and deployed a pristine master branch as a docker image, the same issue persists. Unable to figure out why building your own image results in "Connect" not being enabled, even for regular sources like Postgres using the SQLAlchemy URI option.
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13691093
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Superset + Opensearch integration
<!-- Answer -->
The `'odelasticsearch'` dialect is commented out in Superset's dialect mapping, so Superset defaults to a generic SQL dialect for query parsing and generation. This fallback uses backticks for quoting identifiers (e.g., `FROM \`default\`.logs`), which Opensearch SQL does not support, leading to parsing errors when creating datasets or running internal queries [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py).
Currently, there is no built-in workaround in Superset for this issue. The `SQL_QUERY_MUTATOR` config can alter outgoing queries, but it does not reliably affect internal queries like those used for dataset metadata [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py). Superset does allow for extending SQL dialects via `SQLGLOT_DIALECTS_EXTENSIONS`, but this only works if the dialect is referenced in the code, which is not the case for `'odelasticsearch'` right now.
To resolve this long-term, a new or updated dialect for Opensearch would need to be contributed to Superset, either by implementing a custom engine spec/plugin or by submitting a pull request to add proper dialect support [[source]](https://github.com/apache/superset/discussions/31619). Until then, the backtick quoting issue will persist for internal queries with Opensearch connections.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=18231ef1-9d1e-4079-8566-03509107eb1a) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13680873
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Superset + Opensearch integration
<!-- Answer -->
Superset fails to parse queries with backticks for Opensearch because its internal SQL parser (sqlglot) doesn't know how to handle Opensearch-specific syntax. The core issue is that Superset does not map the 'odelasticsearch' engine to any sqlglot dialect in its SQLGLOT_DIALECTS configâit's commented out in the code. As a result, Superset defaults to a generic dialect that doesn't recognize backtick-quoted identifiers, causing the parsing error before the query ever reaches Opensearch, even though Opensearch itself supports and expects backticks for delimited identifiers. This failure happens entirely inside Superset's parsing step, not in query construction or in Opensearch itself.
To fix this, Superset would need a dialect mapping for 'odelasticsearch' that supports backtick quoting, either by adding it to SQLGLOT_DIALECTS or by extending dialects via SQLGLOT_DIALECTS_EXTENSIONS and ensuring the parser recognizes backticks for this engine. Until that's done, this parsing error will persist for internal queries using backticks, even if those queries are valid for Opensearch.
[Reference: code and config](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py)
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=af857e4e-f1a7-414d-a6ad-bf4f9478d984) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13681398
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Superset + Opensearch integration
<!-- Answer -->
Superset fails to parse queries with backticks for Opensearch because its internal SQL parser (sqlglot) doesn't know how to handle Opensearch-specific syntax. The core issue is that Superset does not map the 'odelasticsearch' engine to any sqlglot dialect in its SQLGLOT_DIALECTS configâit's commented out in the code. As a result, Superset defaults to a generic dialect that doesn't recognize backtick-quoted identifiers, causing the parsing error before the query ever reaches Opensearch, even though Opensearch itself supports and expects backticks for delimited identifiers. This failure happens entirely inside Superset's parsing step, not in query construction or in Opensearch itself.
To fix this, Superset would need a dialect mapping for 'odelasticsearch' that supports backtick quoting, either by adding it to SQLGLOT_DIALECTS or by extending dialects via SQLGLOT_DIALECTS_EXTENSIONS and ensuring the parser recognizes backticks for this engine. Until that's done, this parsing error will persist for internal queries using backticks, even if those queries are valid for Opensearch.
[Reference: code and config](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/sql/parse.py)
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=hallucination) | [Report đ](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/af857e4e-f1a7-414d-a6ad-bf4f9478d984?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34083)
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13681398
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "serverdevil (via GitHub)" <gi...@apache.org>.
GitHub user serverdevil added a comment to the discussion: Superset + Opensearch integration
`opensearch`'s sql rest api states that opensearch supports delimited identifiers using backticks. Also the query above when made directly to opensearch using url like below works fine
```
curl -XPOST http://localhost:9200/_plugins/_sql -u 'admin:admin' -k -H 'Content-Type: application/json' -d '{"query": "SELECT * FROM `default`.logs LIMIT 50"}'
{
"schema": [
{
"name": "log",
"type": "text"
},
{
"name": "@timestamp",
"type": "timestamp"
}
],
"datarows": [
[
"2025-07-04T10:15:01.057694+00:00 ip-172-31-8-180 CRON[1581970]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)",
"2025-07-04 10:15:01.058"
],
[
"2025-07-04T10:15:01.066223+00:00 ip-172-31-8-180 CRON[1581970]: pam_unix(cron:session): session closed for user root",
"2025-07-04 10:15:01.066"
],
...
}
```
So the question now is, why does superset, who is constructing the query correctly using backticks around default, failing to parse the query on it's end?
Thanks @dosu but really hoping some expert can shed some light in the right direction. Anyone?
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-13681355
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset + Opensearch integration [superset]
Posted by "Vitor-Avila (via GitHub)" <gi...@apache.org>.
GitHub user Vitor-Avila added a comment to the discussion: Superset + Opensearch integration
@serverdevil in case you're still stuck here, I'm working on an OpenSearch dialect that could help fixing this issue: https://github.com/apache/superset/pull/39538
GitHub link: https://github.com/apache/superset/discussions/34083#discussioncomment-16665209
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org