[
https://issues.apache.org/jira/browse/HIVE-27264?focusedWorklogId=857301&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-857301
]
ASF GitHub Bot logged work on HIVE-27264:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Apr/23 08:08
Start Date: 17/Apr/23 08:08
Worklog Time Spent: 10m
Work Description: kasakrisz commented on code in PR #4237:
URL: https://github.com/apache/hive/pull/4237#discussion_r1168331370
##########
ql/src/test/queries/clientpositive/pointlookup6.q:
##########
@@ -0,0 +1,17 @@
+create table r_table (
Review Comment:
Changing `hive.optimize.point.lookup` to `false` changes the plan in the
test output so I wouldn't add this explicitly. It would also turn off the whole
point lookup optimization functionality and in general we don't want to turn
off any functionality because it would lead to dead functionalities and make
very hard to re-enable it after a while.
I added
```
set hive.optimize.point.lookup.min=2
```
It makes sense in this test case since we have only two constants in the
`IN` expressions.
Issue Time Tracking
-------------------
Worklog Id: (was: 857301)
Time Spent: 40m (was: 0.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: 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)
