Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/7920#issuecomment-127677256
It would be good to improve `sameResult`, but I think that is much to scary
of a change to merge in after feature freeze. Query subsumption is hard, and
while what we do today is limited, it is simple and easy to reason about. Past
attempts to improve this function have had subtle correctness bugs.
Regarding checking in a lot of places, we already have to check for
`child.resolved` in many places already. Depending on time, I'll look at
migrating this logic into a special version of transform, where we can be even
more efficient.
---
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]
