alamb commented on PR #21829: URL: https://github.com/apache/datafusion/pull/21829#issuecomment-4347412023
> Pre-resolving before planning means either: > > * Opening everything (expensive, defeats the purpose of predicate pruning), or > * Blocking on a synchronous call that itself needs to peek at the predicate at which point you've re-implemented an analysis rule, just outside the planner (which is our current approach) I think peeking at the predicates is unavaoidable in the usecase you describe -- DataFusion planning in general requires knowledge of the schema. Thus sort of by definition you can't really start planning (e.g. making LogicalPlan/Expr) until you have access to the schemas. I am not sure the current system has a concrete notion of a "partially-analyed" plan For your case, I think you will basically need to look at the unplanned query (peek at the parse tree), resolve the schema you want to use, and then proceed with normal planning -- 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]
