Github user davies commented on the pull request:
https://github.com/apache/spark/pull/10935#issuecomment-204658130
@xguo27 Thanks for working on this. I think the root cause here is that we
extract Python UDFs too early (in analyzer), EvaluatePython is an special
logical plan, many rules have no knowledge of it, which will break many things.
We should extract Python UDFs later, in end of optimizer, or physical plan, I
will send an PR to fix that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
