Hi Luca, The way forward that we’re recommending now is to connect via SqlAlchemy if at all possible. There are some limitations in the SqlAlchemy connector, and the SQL interface is only available in more-recent versions, which is the reason for the continued existence of the API-based connector.
I hope that clears things up! Will Barrett Staff Software Engineer Preset, Inc. | https://preset.io On Apr 7, 2020, 5:36 AM -0700, Luca Toscano <toscano.l...@gmail.com>, wrote: > Hi everybody, > > On Tue, Apr 7, 2020 at 11:51 AM Ville Brofeldt > <ville.v.brofe...@gmail.com> wrote: > > > A few notes on known issues with this Release Candidate: > > - When rendering a TableViz with the legacy Druid connector, a cryptic > > error message is raised if the query doesn't return any data. A PR #9480 to > > address this is pending final review and merging. As this is affecting a > > deprecated feature in Superset, this was not regarded as a blocker for this > > release. > > just to be clear, what is the right/supported way to query Druid? Via > SqlAlchemy (TIL that this is a possibility) ? Just asking to think > about what to suggest to users of Superset where I work, since we rely > a lot on it and I'd love use the best supported path. > > Thanks! > > Luca
