alamb commented on issue #14256: URL: https://github.com/apache/datafusion/issues/14256#issuecomment-2614323152
> I located the biggest jump happens on [#11681](https://github.com/apache/datafusion/pull/11681), commit [3438b35](https://github.com/apache/datafusion/commit/3438b355308afa23dba399f4aec5760969d054c5). But I can't tell the reason. I go through it and it's just a normal logic change patch, no new dep or feature was introduced 🤔 I wonder if the new analyzer rule caused the jump 🤔 (`datafusion/optimizer/src/analyzer/expand_wildcard_rule.rs`) One theory could be that the tree node walking code is substantial and slow to compile (it is a lot of templates 🤔 ) However, a new analyzer rule in `datafusion-optimizer` doesn't explain longer compile times in the `datafusion` crate 🤔 -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
