Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 13A28200C7D for ; Tue, 16 May 2017 20:47:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 123C8160BC1; Tue, 16 May 2017 18:47:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 59B40160BA6 for ; Tue, 16 May 2017 20:47:07 +0200 (CEST) Received: (qmail 93902 invoked by uid 500); 16 May 2017 18:47:06 -0000 Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list notifications@asterixdb.apache.org Received: (qmail 93893 invoked by uid 99); 16 May 2017 18:47:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 May 2017 18:47:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 18505C030F for ; Tue, 16 May 2017 18:47:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 22W_fBp3Gm05 for ; Tue, 16 May 2017 18:47:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1884A5FCC4 for ; Tue, 16 May 2017 18:47:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A87AFE09D6 for ; Tue, 16 May 2017 18:47:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5E96721940 for ; Tue, 16 May 2017 18:47:04 +0000 (UTC) Date: Tue, 16 May 2017 18:47:04 +0000 (UTC) From: "Taewoo Kim (JIRA)" To: notifications@asterixdb.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ASTERIXDB-1762) AQL+ needs to be revised. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 16 May 2017 18:47:08 -0000 [ https://issues.apache.org/jira/browse/ASTERIXDB-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012910#comment-16012910 ] Taewoo Kim commented on ASTERIXDB-1762: --------------------------------------- Step 2 of 2 done: AQLPlus Refactoring 2: AQL+ grammar generation and AQLPlusExpressionToPlanTranslator https://asterix-gerrit.ics.uci.edu/#/c/1434/ as of Feb 2017. > AQL+ needs to be revised. > -------------------------- > > Key: ASTERIXDB-1762 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1762 > Project: Apache AsterixDB > Issue Type: Improvement > Reporter: Taewoo Kim > Assignee: Taewoo Kim > > AQL+ is a super set of AQL (two differences: meta-variable and meta-clause), and is used to transform the given plan using a rewritten AQL+ statements. Using AQL+ to construct AQL+ statements and translate it to expressions and a plan, the sub plan of the given operator as well as the operator itself can be transformed into a new plan. > Currently, AQL+ is not synced with AQL grammar. Actually, it only uses a certain portion of AQL constructs in one rule - FuzzyJoinRule. Since AQL+ is a super set of AQL and the concepts (meta-variable and meta-clause) of AQL+ is not used by other AQL constructs, I think we can integrate AQL and AQL+. > 1) Integrate AQL and AQL+ > Then, we do not need to maintain separate grammar and ExpressionToPlan Translator. And since normal AQL grammar doesn't interfere with AQL+ grammar (we never expose the AQL+ grammar to the user level). Currently, FuzzyJoin requires AQL+ functionality to build the transformed plan. Unless we want to introduce the massive number of operators in hand in the plan, I think it's better remove separate grammar and integrate it with AQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)