Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16193
If we add a logical node for python evaluator, we'd push down the Filter
through it, so the optimizer rule won't combine two Filter into one again?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
