alamb commented on issue #9111: URL: https://github.com/apache/arrow-datafusion/issues/9111#issuecomment-1926784866
> All expressions can be rewritten if a change occurs in the plan because of this kind of index changes. Right -- I think the difference is that in the Physical realm, projection pushdown could maintain the mapping of "is output column N used" where N is the index. Then the trick will be to implement the transformation for each type of ExecutionPlan to both: 1. Rewrite itself if one of its output columns is not used 2. Describe which of the columns on the input are required to create its output With thse two functions I think you could implement a pretty simple pushdown rule -- 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]
