Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/8983#issuecomment-146266287
I think we are all in agreement that `null IN (...)` should return null.
The only question here is if we should through an error when the stuff in
`(...)` can be coerced to a common type. It seems to me that the user must be
confused if they are attempting to compare a value with an incompatible set of
options. It would be good to see what other systems do here.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
