Return-Path: X-Original-To: apmail-asterixdb-dev-archive@minotaur.apache.org Delivered-To: apmail-asterixdb-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D7A310A5C for ; Mon, 14 Sep 2015 17:20:48 +0000 (UTC) Received: (qmail 11777 invoked by uid 500); 14 Sep 2015 17:20:48 -0000 Delivered-To: apmail-asterixdb-dev-archive@asterixdb.apache.org Received: (qmail 11727 invoked by uid 500); 14 Sep 2015 17:20:48 -0000 Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.incubator.apache.org Delivered-To: mailing list dev@asterixdb.incubator.apache.org Received: (qmail 11702 invoked by uid 99); 14 Sep 2015 17:20:47 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2015 17:20:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9381818041A for ; Mon, 14 Sep 2015 17:20:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.774 X-Spam-Level: * X-Spam-Status: No, score=1.774 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.006] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nvr3j9vgGq7A for ; Mon, 14 Sep 2015 17:20:47 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id D749220562 for ; Mon, 14 Sep 2015 17:20:46 +0000 (UTC) Received: (qmail 11317 invoked by uid 99); 14 Sep 2015 17:20:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2015 17:20:46 +0000 Date: Mon, 14 Sep 2015 17:20:46 +0000 (UTC) From: "Till Westmann (JIRA)" To: dev@asterixdb.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ASTERIXDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Westmann updated ASTERIXDB-1086: ------------------------------------- Component/s: Optimizer AsterixDB > 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 > > 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)