dosubot[bot] commented on issue #35270: URL: https://github.com/apache/superset/issues/35270#issuecomment-3330019518
<!-- Answer --> This issue is likely related to how Superset handles SQL dialects and identifier escaping for Pinot. There have been known problems where Superset generated queries using MySQL-style syntax (like backticks or incorrect quoting), which Pinot does not support. This caused charts to fail or return incorrect results, especially when using reserved words or quoted identifiers like `"name"`. A fix for the SQL dialect issue was merged into the master branch, but if you're still seeing problems, it may be due to how identifier quoting is handled in the Pinot engine spec or the underlying SQLAlchemy dialect. Superset's Pinot integration does not explicitly strip or modify quotes from field names, so issues can arise if the dialect logic is too generic or not fully aligned with Pinot's requirements. There was also a recent fix for a related bug where string escaping logic was incorrectly shared between dialects, which could have affected Pinot as well [see details](https://github.com/apache/superset/pull/34895). If you haven't already, try the workaround of removing the `'pinot'` entry from the SQL parser configuration (`superset/sql/parse.py`) as described in recent issues [here](https://github.com/apache/superset/issues/34856). This forces Superset to avoid using MySQL-style syntax for Pinot queries. If the problem persists, it may help to test with other quoted columns to see if the issue is specific to `"name"` or affects all quoted identifiers. Also, check if your Superset instance includes the latest fixes from the master branch, as these address several dialect and escaping bugs for Pinot [reference](https://github.com/apache/superset/issues/34700). <!-- 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/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c303433c-f97b-48a1-902f-4bd19eaceca4?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](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/issues/35270) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org