You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
In IOx we have several extension nodes with Exprs which we want to compile to PhysicalExpr as part of a plan
This was previously annoying as the signature of the extension planner is:
However, with the introduction of qualified names, now I have to provide a DFSchema (which should have come from the input LogicalPlan which I do not have access to at this point).
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
In IOx we have several extension nodes with
Expr
s which we want to compile toPhysicalExpr
as part of a planThis was previously annoying as the signature of the extension planner is:
Which offers no way to plan physical expressions, so I had to do something like the following workaround
However, with the introduction of qualified names, now I have to provide a
DFSchema
(which should have come from the input LogicalPlan which I do not have access to at this point).(note the "foo" needs to be the correct table name"
Describe the solution you'd like
create_physical_expr
to thePhysicalPlanner
traitctx_state
)Basically as the internals of DataFusion evolve we also need to evolve the interfaces along with it.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: