Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7778#issuecomment-126184508
actually now i think about it more, in most cases it's probably a lot
faster to just use the generated code for IN compared with a hashset lookup. In
the case of a hashset lookup, it might make sense to change the OptimizeIn rule
to only convert In to InSet if the number of instances is greater than say 50.
---
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]
