feralberca opened a new issue #18930: URL: https://github.com/apache/superset/issues/18930
We are experiencing some issues when querying Druid using Superset. It seems that Superset is trying to optimize the query based on its content (group by, order by) which cause to use different Druid apis for solving the query (timeseries vs topN). As an example if I have a query with a group by clause and add some aggregation like count(), adding an order by on a field that I'm using for grouping should not change the query outcome which is what is happening now. Instead, if I query Druid directly I always get the same results with or without the order by. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
