Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
Date: Thu, 18 Aug 2016 21:53:20 +0000 (UTC)
From: "Taewoo Kim (JIRA)" <jira@apache.org>
To: notifications@asterixdb.incubator.apache.org
Message-ID: <JIRA.12862875.1441835905000.349393.1471557200455@Atlassian.JIRA>
In-Reply-To: <JIRA.12862875.1441835905000@Atlassian.JIRA>
References: <JIRA.12862875.1441835905000@Atlassian.JIRA> <JIRA.12862875.1441835905059@arcas>
Subject: [jira] [Commented] (ASTERIXDB-1086) IntroduceProjectsRule creates a
 wrong PROJECT operator when there are multiple paths.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 Aug 2016 21:53:24 -0000


    [ https://issues.apache.org/jira/browse/ASTERIXDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427229#comment-15427229 ] 

Taewoo Kim commented on ASTERIXDB-1086:
---------------------------------------

This is part of index-only change and is uploaded as a patch set:
https://asterix-gerrit.ics.uci.edu/#/c/1073/

> IntroduceProjectsRule creates a wrong PROJECT operator when there are multiple paths.
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1086
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1086
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Optimizer
>            Reporter: Taewoo Kim
>            Assignee: Taewoo Kim
>              Labels: with-index-only
>
> IntroduceProjectsRule introduce a wrong project to filter out a variable that is used in the one of two paths after SPLIT (REPLICATE) operator. In my branch, I am trying to optimize the index-search. In order to implement this, there is an ASSIGN operator and it assigns a variable that is going to be used in the SELECT operator. After ASSIGN, there is SPLIT operator. It divides the path into two - the left path contains the SELECT and the other path contains no operator. Two paths will be merged by UNION operator. The issue is IntroduceProjectRule can't consider all paths at the same time. Thus, when it checks the right path, it introduces a wrong PROJECT operator that filters out one variable in the ASSIGN before SPLIT since it thinks that the variable is not used after ASSIGN operator. In fact, the variable is used in the left path.


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