[
https://issues.apache.org/jira/browse/ASTERIXDB-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550179#comment-16550179
]
ASF subversion and git services commented on ASTERIXDB-2415:
------------------------------------------------------------
Commit fa03c20ff82894054d397d6efe862ff7aa96e36d in asterixdb's branch
refs/heads/master from [~idleft]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=fa03c20 ]
[ASTERIXDB-2415][COMP] Type inference fix in InjectTypeCastForSwitchCaseRule
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
For dual inputs operator, its type inference should start from current
Op so that it wouldn't fail for the join case when there are variable
usages in conditions from the 2nd branch.
Change-Id: I7c18bc58381bab2c25d1e58ee7bab7f1b2aaf440
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2769
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Xikui Wang <[email protected]>
> InjectTypeCastForSwitchCaseRule type inference exception
> --------------------------------------------------------
>
> Key: ASTERIXDB-2415
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2415
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Xikui Wang
> Priority: Major
>
> The type inference for InjectTypeCastForSwitchCaseRule should start from the
> current Op, instead of its first input. In a JOIN case, the type inference
> would fail if there is an expression in the condition that uses variables
> from another branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
