You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Jason Dere (JIRA)" <ji...@apache.org> on 2018/07/18 19:36:00 UTC
[jira] [Created] (HIVE-20204) Type conversion during IN ()
comparisons is using different rules from other comparison operations
Jason Dere created HIVE-20204:
---------------------------------
Summary: Type conversion during IN () comparisons is using different rules from other comparison operations
Key: HIVE-20204
URL: https://issues.apache.org/jira/browse/HIVE-20204
Project: Hive
Issue Type: Bug
Components: Types
Reporter: Jason Dere
Assignee: Jason Dere
Noticed this while looking at HIVE-20082.
The type conversion done during GenericUDFIn (via ReturnObjectInspectorResolver) uses FunctionRegistry.getCommonClass(), whereas the other comparison operators (=, <, >, <=, >=) use FunctionRegistry.getCommonClassForComparison(). As a result, dec_column IN ('1.1', '2.2') compares the values as strings, whereas dec_column = '1.1' would compare the values as doubles. This makes a difference for HIVE-20082 since it is related to changing the 0-padding during decimal-to-string conversions.
cc [~ashutoshc]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)