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 2018/10/26 00:47:00 UTC

[jira] [Assigned] (HIVE-20617) Fix type of constants in IN expressions to have correct type

     [ https://issues.apache.org/jira/browse/HIVE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesus Camacho Rodriguez reassigned HIVE-20617:
----------------------------------------------

    Assignee: Jesus Camacho Rodriguez  (was: Zoltan Haindrich)

> Fix type of constants in IN expressions to have correct type
> ------------------------------------------------------------
>
>                 Key: HIVE-20617
>                 URL: https://issues.apache.org/jira/browse/HIVE-20617
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Zoltan Haindrich
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>         Attachments: HIVE-20617.01.patch, HIVE-20617.02.patch, HIVE-20617.03.patch, HIVE-20617.05.patch, HIVE-20617.06.patch, HIVE-20617.07.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.08.patch, HIVE-20617.09.patch, HIVE-20617.10.patch, HIVE-20617.10.patch, HIVE-20617.11.patch, HIVE-20617.11.patch, HIVE-20617.12.patch
>
>
> In statements like {{struct(a,b) IN (const struct('x','y'), ... )}} the comparision in UDFIn may fail because if a or b is of char/varchar type the constants will retain string type - especially after PointlookupOptimizer compaction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)