You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (Jira)" <ji...@apache.org> on 2020/04/26 19:14:00 UTC
[jira] [Updated] (HIVE-23222) Missed opportunity in IN merge
[ https://issues.apache.org/jira/browse/HIVE-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesus Camacho Rodriguez updated HIVE-23222:
-------------------------------------------
Target Version/s: 4.0.0
> Missed opportunity in IN merge
> ------------------------------
>
> Key: HIVE-23222
> URL: https://issues.apache.org/jira/browse/HIVE-23222
> Project: Hive
> Issue Type: Improvement
> Components: CBO
> Affects Versions: 4.0.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
>
> After HIVE-23100 went in, there was a missed opportunity merging IN clauses, which can be seen in ql/src/test/results/clientpositive/llap/vector_between_in.q.out .
> {code}
> filterExpr: (cdecimal1) IN (2365.8945945946, 881.0135135135, -3367.6517567568) (type: boolean)
> {code}
> was replaced by:
> {code}
> filterExpr: ((cdecimal1) IN (2365.8945945946, -3367.6517567568) or (cdecimal1) IN (881.0135135135)) (type: boolean)
> {code}
> The problem seems to be that with decimal type, we are considering values with different precision/scale as a different type, thus we do not merge them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)