alamb commented on issue #17297: URL: https://github.com/apache/datafusion/issues/17297#issuecomment-3265746364
> Looks like create memory table will be handled by datafusion context > > [datafusion/datafusion/core/src/execution/context/mod.rs](https://github.com/apache/datafusion/blob/fd7df66724f958a2d44ba1fda1b11dc6833f0296/datafusion/core/src/execution/context/mod.rs#L662) > > Line 662 in [fd7df66](/apache/datafusion/commit/fd7df66724f958a2d44ba1fda1b11dc6833f0296) > > pub async fn execute_logical_plan(&self, plan: LogicalPlan) -> Result<DataFrame> { > [datafusion/datafusion/core/src/execution/context/mod.rs](https://github.com/apache/datafusion/blob/fd7df66724f958a2d44ba1fda1b11dc6833f0296/datafusion/core/src/execution/context/mod.rs#L807-L808) > > Lines 807 to 808 in [fd7df66](/apache/datafusion/commit/fd7df66724f958a2d44ba1fda1b11dc6833f0296) > > async fn create_memory_table(&self, cmd: CreateMemoryTable) -> Result<DataFrame> { > let CreateMemoryTable { > So it looks like create memory table will not be propagated to custom query planner. What we do in InfluxDB is basically override `sql` and specially handle all the DDL commands -- maybe ballista could do the same 🤔 -- 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]
