You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/02/26 23:50:33 UTC

[GitHub] [druid] sascha-coenen edited a comment on issue #9413: SQL: BLOOM_FILTER() does not work on constant values fed in via sub query

sascha-coenen edited a comment on issue #9413: SQL: BLOOM_FILTER() does not work on constant values fed in via sub query
URL: https://github.com/apache/druid/issues/9413#issuecomment-591703412
 
 
   thanks for the explanations.
   
   What I did not understand is that Druid can't handle FROM (VALUES ...) yet.
   It seems to work at least partially as the following query works fine:
   `
   SELECT COUNT(blacklist.item) FROM (VALUES 'a', 'b', 'c') AS blacklist (item)
   `
   
   > meaning all Druid SQL queries will actually run as Druid native queries
   
   sounds definitely interesting although I'm not sure whether I understand correctly.
   Does it mean that historicals would support receiving SQL queries directly and being able to execute them without having to rewrite them to JSON queries first? And that can be done without calcite? wow

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


With regards,
Apache Git Services

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