[
https://issues.apache.org/jira/browse/CALCITE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648181#comment-14648181
]
Julian Hyde commented on CALCITE-824:
-------------------------------------
Looks great. Yes, it is the right fix. I hardened the test case a bit, and I
have committed as my branch
https://github.com/julianhyde/incubator-calcite/tree/824-semijoin-inference. I
will commit to apache when release 1.4 is done. Thanks for the patch!
By the way, it is a propos... I am re-working IN in CALCITE-816, so I'll make
sure that your test case continues to work.
> 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: next
>
> 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)
