gianm commented 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-591705590 > 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 What I meant was that today there are two ways that Druid SQL queries can run: - If they refer to Druid datasources then they will be translated to native Druid queries and run that way. - If they do not refer to Druid datasources, they run using Calcite's interpreter. This includes any queries on `sys` or `INFORMATION_SCHEMA` tables, and any queries on raw `VALUES`. It is a bit weird to have two paths like this, and we'd like to standardize on always translating SQL to native Druid queries (the JSON ones). This means native Druid queries need to start supporting functionality like `sys`, `INFORMATION_SCHEMA`, `VALUES`, etc. It is coming but we aren't quite there yet.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
