[jira] [Work logged] (HIVE-27264) Literals in conjunction of two in expression are considered not equals if type precision is different

[ASF GitHub Bot (Jira)]

     [ 
https://issues.apache.org/jira/browse/HIVE-27264?focusedWorklogId=857667&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-857667
 ]

ASF GitHub Bot logged work on HIVE-27264:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Apr/23 12:06
            Start Date: 18/Apr/23 12:06
    Worklog Time Spent: 10m 
      Work Description: kasakrisz commented on PR #4237:
URL: https://github.com/apache/hive/pull/4237#issuecomment-1512971441

   @zabetak 
   It is happening in `HivePointLookupOptimizerRule`
   
https://github.com/apache/hive/blob/f6ac8d480f93147c6deb4d86f0462edbb45d3fa4/ql/src/java/org/apache/hadoop/hive/ql/optimizer/calcite/rules/HivePointLookupOptimizerRule.java#L717
   
   And introduced by https://issues.apache.org/jira/browse/HIVE-24154




Issue Time Tracking
-------------------

    Worklog Id:     (was: 857667)
    Time Spent: 1h 40m  (was: 1.5h)

> Literals in conjunction of two in expression are considered not equals if 
> type precision is different
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-27264
>                 URL: https://issues.apache.org/jira/browse/HIVE-27264
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> {code}
> create table r_table (
>   string_col varchar(30)
> );
> create table l_table (
>   string_col varchar(14)
> );
> insert into r_table VALUES ('AAA111');
> insert into l_table VALUES ('AAA111');
> SELECT l_table.string_col from l_table, r_table
> WHERE r_table.string_col = l_table.string_col AND l_table.string_col IN 
> ('AAA111', 'BBB222') AND r_table.string_col IN ('AAA111', 'BBB222');
> {code}
> Should give one row
> {code}
> AAA111
> {code}
> but it returns empty rs
> Workaround
> {code}
> set hive.optimize.point.lookup=false;
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)