Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11682#issuecomment-196423960
@gatorsmile Thanks for finding this. In general, both
PushPredicateThroughProject and ColumnPruning are useful, we should keep both
and fix the conflict (make them stable).
I think they are only conflicted with each other when they are on opt of a
LeafNode (can't be pushed further), so we don't need to insert a Project
between Filter and LeafNode, because PhysicalOperation can already handle
Project(Filter(LeafNode())) very well.
For the non-deterministic Filter or Project, we may do things wrong in many
places, could you create a separate JIRA for 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]
