Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16193
@gatorsmile I do mean that we don't push down predicates into `ExistingRDD`
scan as it doesn't help generally. But `BatchEvalPython` is a special case.
It doesn't matter `ExistingRDD` is the child of `Filter` or not. We already
do the similar predicate pushdown in the rules like `FileSourceStrategy`.
If we push down predicates into `ExistingRDD` scan node during query
planning. We can avoid to do predicate pushdown in SparkPlan. I think it is not
a good idea.
---
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]
