avantgardnerio commented on issue #3283: URL: https://github.com/apache/arrow-datafusion/issues/3283#issuecomment-1230476980
This is a really interesting aspect of optimizer rules I've encountered before, and am not sure how to best address: 1. We can run them in a particular order - this is brittle and changing the order or running them twice can break things. They become very hard-coded to rely on that order over time. 2. We could run them iteratively until we detect no change to the plan, or we reach a "max depth" where we give up and just run the plan. I'm curious how other optimizers handle this. -- 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]
