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 [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
