[
https://issues.apache.org/jira/browse/HIVE-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058221#comment-13058221
]
Hudson commented on HIVE-2248:
------------------------------
Integrated in Hive-trunk-h0.21 #803 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/803/])
HIVE-2248 Comparison Operators convert number types to common type instead
of
double if necessary (Siying Dong via namit)
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1141777
Files :
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFBaseCompare.java
> Comparison Operators convert number types to common type instead of double if
> necessary
> ---------------------------------------------------------------------------------------
>
> Key: HIVE-2248
> URL: https://issues.apache.org/jira/browse/HIVE-2248
> Project: Hive
> Issue Type: Bug
> Reporter: Siying Dong
> Assignee: Siying Dong
> Attachments: HIVE-2248.1.patch
>
>
> Now if the two sides of comparison is of different type, we always convert
> both to double and compare. It was a slight regression from the change in
> https://issues.apache.org/jira/browse/HIVE-1638. The old UDFOP<Comparison>,
> using GenericUDFBridge, always tried to find common type first.
> The worse case is this: If you did "WHERE <BIGINT_COLUMN> = 0 ", we always
> convert the column and 0 to double and compare, which is wasteful, though it
> is usually a minor costs in the system. But it is easy to fix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
