Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB0C2172E4 for ; Mon, 23 Mar 2015 19:42:52 +0000 (UTC) Received: (qmail 62399 invoked by uid 500); 23 Mar 2015 19:42:52 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 62365 invoked by uid 500); 23 Mar 2015 19:42:52 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 62355 invoked by uid 99); 23 Mar 2015 19:42:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 19:42:52 +0000 Date: Mon, 23 Mar 2015 19:42:52 +0000 (UTC) From: "Chris Westin (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-2527) Query profile displays operatorId=11 twice for same major and minor fragments 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/DRILL-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Westin updated DRILL-2527: -------------------------------- Fix Version/s: 1.0.0 > Query profile displays operatorId=11 twice for same major and minor fragments > ----------------------------------------------------------------------------- > > Key: DRILL-2527 > URL: https://issues.apache.org/jira/browse/DRILL-2527 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow > Affects Versions: 0.9.0 > Reporter: Krystal > Assignee: Venki Korukanti > Fix For: 1.0.0 > > > git.commit.id=4d398edf87d2ec6fab6c552b1f5a33fb31b955bc > The query profile for completed queries contain 2 entries for operatorType=11 (UNORDERED_RECEIVER) for the same major and minor fragment. Here is an example: > 0: jdbc:drill:schema=dfs.hbase> select t3.majorId, t3.minfid,t3.oProfile.operatorType operator_type from (select t2.majorFragmentId majorId,t2.minorFragmentProfile.minorFragmentId minfid,flatten(t2.minorFragmentProfile.operatorProfile) oProfile from (select t1.col.majorFragmentId majorFragmentId, flatten(t1.col.minorFragmentProfile) minorFragmentProfile from (select flatten(t.fragmentprofile) col from `dfs.drillTestDir`.`/ui_profiles/query1.json`t) t1) t2) t3 where t3.majorId=2 and t3.oProfile.operatorType=11; > +------------+------------+---------------+ > | majorId | minfid | operator_type | > +------------+------------+---------------+ > | 2 | 0 | 11 | > | 2 | 0 | 11 | > | 2 | 2 | 11 | > | 2 | 2 | 11 | > | 2 | 1 | 11 | > | 2 | 1 | 11 | > +------------+------------+---------------+ > The metrics for the first entry of each set is always 0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)