Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10296#issuecomment-164963594
Hey guys, I think all this nullability clean up is great, but I afraid that
the changes to `BoundReference` are in conflict with something @nongli and
@davies are trying to accomplish. Basically, for performance reasons we should
be able to skip null checks for columns that are not nullable since bitset
operations and branches are pretty expensive. If we are trying to solve
SPARK-12323 then I think the right place to do it is probably in `NewInstance`.
---
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]
