You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/13 05:19:00 UTC
[jira] [Updated] (ARROW-11617) [C++][Gandiva] Fix nested if-else
optimisation in gandiva
[ https://issues.apache.org/jira/browse/ARROW-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-11617:
-----------------------------------
Labels: pull-request-available (was: )
> [C++][Gandiva] Fix nested if-else optimisation in gandiva
> ---------------------------------------------------------
>
> Key: ARROW-11617
> URL: https://issues.apache.org/jira/browse/ARROW-11617
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Projjal Chanda
> Assignee: Projjal Chanda
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {color:#1d1c1d}In gandiva, when we have nested if-else statements we reuse the local bitmap and treat it is a single logical if - elseif - .. - --else condition. However, when he have say another function between them like{color}
> {color:#1d1c1d}IF{color}
> {color:#1d1c1d}THEN{color}
> {color:#1d1c1d}ELSE{color}
> {color:#1d1c1d}function({color}
> {color:#1d1c1d}IF{color}
> {color:#1d1c1d}THEN{color}
> {color:#1d1c1d}ELSE{color}
> {color:#1d1c1d}){color}
> {color:#1d1c1d}in such cases also currently we are doing same thing which can lead to incorrect results{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)