Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10362#issuecomment-165616917
To be honest, I did the exactly same fix at the beginning, because this
hole is so large. Then, after running more test cases, I realized the current
strategy is very tricky. It can process all the cases except `Not`. Only the
`Not` operator changes the inner `And` and `Or`. Thus, maybe we still can keep
the current aggressive push-down strategy. I am wondering who did this initial
design? : )
---
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]
