YifanZhang created KUDU-3564:
--------------------------------
Summary: Range specific hashing table when queried with InList
predicate may lead to incorrect results
Key: KUDU-3564
URL: https://issues.apache.org/jira/browse/KUDU-3564
Project: Kudu
Issue Type: Bug
Affects Versions: 1.17.0
Reporter: YifanZhang
Reproduce steps that copy from the Slack channel:
create the table and data in Impala:
// create the table and data in Impala:
CREATE TABLE age_table
(
id BIGINT,
name STRING,
age INT,
PRIMARY KEY(id,name,age)
)
PARTITION BY HASH (id) PARTITIONS 4,
HASH (name) PARTITIONS 4,
range (age)
(
PARTITION 30 <= VALUES < 60,
PARTITION 60 <= VALUES < 90
)
STORED AS KUDU
TBLPROPERTIES ('kudu.num_tablet_replicas' = '1');
ALTER TABLE age_table ADD RANGE PARTITION 90<= VALUES <120
HASH(id) PARTITIONS 3 HASH(name) PARTITIONS 3;
insert into age_table values (3, 'alex', 50);
insert into age_table values (12, 'bob', 100);
// only predicate "in" for data in custom hash cannot be found,
sudo -u kudu kudu table scan <master.url> default.age_table -columns=id,age
-predicates='["AND", ["IN", "id", [3,20]]]'
(int64 id=3, int32 age=50)
Total count 1 cost 0.0178102 seconds
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
