[
https://issues.apache.org/jira/browse/HIVE-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236343#comment-14236343
]
Ashutosh Chauhan commented on HIVE-9030:
----------------------------------------
This I think is a useful change. Because of casts introduced on cbo path, this
comparison became known at compile time to Hive and thus Hive was able to emit
this warning. On non-cbo, comparison would have still happened, but rather
implicitly at runtime and Hive would miss the opportunity to generate this
warning.
My suggestion is to close this as 'Not a problem'.
> CBO: Plans with comparison of values with different types
> ---------------------------------------------------------
>
> Key: HIVE-9030
> URL: https://issues.apache.org/jira/browse/HIVE-9030
> Project: Hive
> Issue Type: Sub-task
> Components: CBO
> Affects Versions: 0.15.0
> Reporter: Jesus Camacho Rodriguez
> Labels: cbo
> Fix For: 0.15.0
>
>
> If CBO is enabled, tests {{correlationoptimizer8.q}} and
> {{filter_join_breaktask2.q}} throw the following warning:
> {noformat}
> WARNING: Comparing a bigint and a string may result in a loss of precision.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
