[
https://issues.apache.org/jira/browse/HIVE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866335#action_12866335
]
Paul Yang commented on HIVE-801:
--------------------------------
The issue with using GenericUDFField is that it requires that all argument
types to be the same. e.g. field(1, "1") will return 0 because 1 is an integer
while "1" is a string. My implementation of IN allows type conversions so that
1 IN ("1") returns true. If we want to have the same kind of type conversion
behavior, then it's possible to merge the two.
Also, that test was to demonstrate the use case in the JIRA where there's an IN
in the WHERE clause.
> row-wise IN would be useful
> ---------------------------
>
> Key: HIVE-801
> URL: https://issues.apache.org/jira/browse/HIVE-801
> Project: Hadoop Hive
> Issue Type: New Feature
> Reporter: Adam Kramer
> Assignee: Paul Yang
> Attachments: HIVE-801.1.patch
>
>
> SELECT * FROM tablename t
> WHERE IN(12345,key1,key2,key3);
> ...IN would operate on a given row, and return True when the first argument
> equaled at least one of the other arguments. So here IN would return true if
> 12345=key1 OR 12345=key2 OR 12345=key3 (but wouldn't test the latter two if
> the first matched).
> This would also help with https://issues.apache.org/jira/browse/HIVE-783, if
> IN were implemented in a manner that allows it to be used in an ON clause.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
