You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "rusackas (via GitHub)" <gi...@apache.org> on 2026/06/16 18:04:00 UTC
Re: [I] Trino database fails when MongoDB's schema name is "analyze" [superset]
rusackas commented on issue #36067:
URL: https://github.com/apache/superset/issues/36067#issuecomment-4721802602
I think this one's been fixed out from under us by a dependency bump. The parse error was sqlglot tokenizing `analyze` as a Trino keyword instead of an identifier — and #40186 bumped sqlglot 28.10.0 → 30.8.0 back in May, which handles it. Reproducing the exact failing path on current master now works:
```python
SQLScript('SELECT * FROM analyze.events LIMIT 100', engine='trino').format()
# parses & formats fine, no error
```
You were on the older sqlglot when you tested. Closing as resolved, but @iercan if you still hit it on current master / 6.x, give me a shout and I'll reopen.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org