[ https://issues.apache.org/jira/browse/DRILL-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388854#comment-14388854 ]
Krystal edited comment on DRILL-2527 at 3/31/15 5:50 PM: --------------------------------------------------------- Same issue for seen for operator type of PARQUET_WRITER was (Author: knguyen): Same issue for seen for operator type of TEXT_SUB_SCAN > 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)