You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/09/02 03:13:45 UTC

[jira] [Resolved] (CALCITE-824) Type inference when converting IN clause to semijoin

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

Julian Hyde resolved CALCITE-824.
---------------------------------
    Resolution: Fixed

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/5d8a90b8. Thanks for the patch, [~jwills]!

> Type inference when converting IN clause to semijoin
> ----------------------------------------------------
>
>                 Key: CALCITE-824
>                 URL: https://issues.apache.org/jira/browse/CALCITE-824
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating, 1.4.0-incubating
>            Reporter: Josh Wills
>            Assignee: Julian Hyde
>             Fix For: 1.5.0-incubating
>
>         Attachments: CALCITE-824.patch
>
>
> I hit an issue where using an IN clause of int literals would work properly when compared against a BIGINT column when the IN clause had less than 20 values, but would fail when processing more than 20 values. I traced the issue to the way target row types are handled inside of the code that converts the IN clause into a semijoin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)