[HIVE-20204] Type conversion during IN () comparisons is using different rules from other comparison operations

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Types
• Assignee: Jason Dere Assign to me
• Reporter: Jason Dere
• Created: 18/Jul/18 19:35
• Updated: 17/Nov/22 08:55
• Resolved: 23/Jul/18 06:19

Description

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 Ashutosh Chauhan

Issue Links

• relates to: HIVE-20082 HiveDecimal to string conversion doesn't format the decimal correctly - master
• links to: https://reviews.apache.org/r/67970/