pepijnve commented on issue #21231: URL: https://github.com/apache/datafusion/issues/21231#issuecomment-4158047284
What you’re describing is exactly the bit I’m wondering how to solve. A lambda function defines a new naming scope. Which is quite different from any other PhysicalExpr. If we need to assume that any PhysicalExpr can introduce a new concept like lambdas, then what kind of api do we need to be able to deal with that? I’m also thinking something along the lines of a tree traversal where the schema can change in the downward phase, and indices can be remapped in the upward phase. You would need to have the schema available for this though, which is not the case when the projection logic is currently triggered. -- 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]
