gianm opened a new issue #9896: URL: https://github.com/apache/druid/issues/9896
Remove the Bindable query path, meaning all SQL queries can be executed as native queries (or a sequence of concatenated native queries, in the case of UNION ALL). Currently, this path is used for the `sys` and `INFORMATION_SCHEMA` schemas. This would allow simplifying the DruidPlanner, as well as joining across these disparate schemas, in case you wanted to do that for some reason. The approach that comes to mind first is to have the SQL layer generate lazy inline datasources for these special tables using `InlineDataSource.fromIterable`. We need to make sure we don't blow through memory or other resources limits while doing this. (The current Bindable stuff has no resource-limiting facility, so this would be an improvement.) I believe the main prerequisite here is supporting `ORDER BY` on non-aggregating queries, meaning adding sort-by-non-time to the Scan query. It's possible that we could start this off by only supporting it for cases where there is just a single segment involved in the query. I believe this would cover the `sys` and `INFORMATION_SCHEMA` cases. ---------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
