[GitHub] [druid] gianm commented on issue #10282: Druid SQL: A sub-query with expressions returns no data potentially due to an incorrect Query plan.

[GitBox <gi...@apache.org>]

gianm commented on issue #10282:
URL: https://github.com/apache/druid/issues/10282#issuecomment-677862016


   Hmm, in general it should be OK to move a HAVING from an inner query to the WHERE of an outer query. That's what seems to be happening here. It doesn't look like a smoking gun to me. But it's possible it didn't get moved properly.
   
   Unfortunately query plans for multi stage queries can be tough to read. Personally I find it easier to enable request logging on the Broker (https://support.imply.io/hc/en-us/articles/360011745614-Enable-Query-or-Request-logging-for-Druid) and then grab the native query out of the request log.
   
   Could you do that and post it here? It'd be nice to see what the native query is.
   
   (I'm hoping to change the output of explain plan to be more readable in the future.)


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org