From issues-return-5380-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Tue Mar 19 01:48:46 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 09F4A180651 for ; Tue, 19 Mar 2019 02:48:45 +0100 (CET) Received: (qmail 83436 invoked by uid 500); 19 Mar 2019 01:48:45 -0000 Mailing-List: contact issues-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list issues@phoenix.apache.org Received: (qmail 83420 invoked by uid 99); 19 Mar 2019 01:48:45 -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, 19 Mar 2019 01:48:45 +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 8663EC20EB for ; Tue, 19 Mar 2019 01:48:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, 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 6P-LcMCTF1zZ for ; Tue, 19 Mar 2019 01:48:43 +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 5FD4B6118E for ; Tue, 19 Mar 2019 01:32:01 +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 C91AEE2982 for ; Tue, 19 Mar 2019 01:32:00 +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 357FE2459E for ; Tue, 19 Mar 2019 01:32:00 +0000 (UTC) Date: Tue, 19 Mar 2019 01:32:00 +0000 (UTC) From: "chenglei (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (PHOENIX-4618) Optimize out order-by on sort-merge-join when possible MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-4618?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 795533#comment-16795533 ]=20 chenglei edited comment on PHOENIX-4618 at 3/19/19 1:31 AM: ------------------------------------------------------------ [~sangudi], yes , I think it is ok, it is just an optimization for {{Group= By.isOrderPreserving}} .For hash grouping, {{ClientAggregatePlan.getOutputO= rderBys}} return empty {{List}}. was (Author: comnetwork): [~sangudi], yes , I think it is ok, it is just an optimization for {{Group= By.isOrderPreserving}} ,for hash grouping, {{ClientAggregatePlan.getOutputO= rderBys}} return empty {{List}}. > Optimize out order-by on sort-merge-join when possible > ------------------------------------------------------ > > Key: PHOENIX-4618 > URL: https://issues.apache.org/jira/browse/PHOENIX-4618 > Project: Phoenix > Issue Type: Improvement > Reporter: Maryann Xue > Assignee: Maryann Xue > Priority: Major > Fix For: 4.15.0, 5.1.0 > > > To do this, \{{OrderPreservingTracker}} relies solely on primary keys for= inferring alignment between order-by expressions and the input sortedness.= To=C2=A0implement=C2=A0this improvement, we need to have extra information= of sortedness which supports equivalent sorted expressions. For example, > {code}SELECT * FROM T1 JOIN T2 ON T1.a =3D T2.a and T1.b =3D T2.b{code} > The result of the sort-merge-join is sorted on (T1.a, T1.b) and (T2.a, T2= .b) at the same time. > Thus, both 1) > {code}SELECT * FROM T1 JOIN T2 ON T1.a =3D T2.a and T1.b =3D T2.b ORDER B= Y T1.a, T1.b{code} > and 2) > {code}SELECT * FROM T1 JOIN T2 ON T1.a =3D T2.a and T1.b =3D T2.b ORDER B= Y T2.a, T2.b{code} > should avoid doing an extra order-by after the sort-merge-join operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)