You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Volodymyr Vysotskyi (JIRA)" <ji...@apache.org> on 2019/04/15 14:00:00 UTC
[jira] [Resolved] (DRILL-7059) Operator profile does not show JDBC
metrics
[ https://issues.apache.org/jira/browse/DRILL-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Volodymyr Vysotskyi resolved DRILL-7059.
----------------------------------------
Resolution: Duplicate
Fix Version/s: 1.14.0
It was fixed in DRILL-6455.
> Operator profile does not show JDBC metrics
> -------------------------------------------
>
> Key: DRILL-7059
> URL: https://issues.apache.org/jira/browse/DRILL-7059
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Monitoring
> Affects Versions: 1.14.0, 1.15.0
> Environment: Drill 1.14
> Reporter: Aditya Allamraju
> Priority: Major
> Fix For: 1.14.0
>
> Attachments: 23a59a1c-e0bb-d5d2-a686-8c4c9ddc6e0f.sys.drill, 23a59f4b-7424-d19e-3b83-d871c2e58ff8.sys.drill
>
>
> This issue was discovered while debugging a performance issue of a query that is run on an Oracle(via storage plugin) and Hive tables.
>
> Listing the query as below that is taking nearly 4 hrs.
> Oracle table: *e35_eos.finapp.sales*
> Hive table: *hive.temp.sales*
> {code:java}
> SELECT Sum(source_cnt) source_cnt,
> Sum(target_cnt) target_cnt,
> sale_id,
> prod_id,
> cust_id,
> time_id,
> channel_id,
> promo_id,
> quantity_sold,
> amount_sold,
> createddate,
> modifieddate
> FROM (SELECT 1 source_cnt,
> 0 target_cnt,
> sale_id,
> prod_id,
> cust_id,
> time_id,
> Trim(channel_id) CHANNEL_ID,
> promo_id,
> quantity_sold,
> amount_sold,
> createddate,
> modifieddate
> FROM e35_eos.finapp.sales
> UNION ALL
> SELECT 0 source_cnt,
> 1 target_cnt,
> sale_id,
> prod_id,
> cust_id,
> time_id,
> Trim(channel_id) CHANNEL_ID,
> promo_id,
> quantity_sold,
> amount_sold,
> createddate,
> modifieddate
> FROM hive.temp.sales
> WHERE top_rank = 1
> AND header__change_oper <> 'D')
> GROUP BY sale_id,
> prod_id,
> cust_id,
> time_id,
> channel_id,
> promo_id,
> quantity_sold,
> amount_sold,
> createddate,
> modifieddate
> HAVING Sum(source_cnt) <> Sum(target_cnt)
> LIMIT 1000
> {code}
> The Physical Plan shows the step for Operator(02-08). But the "*operator profile*", is missing the step.
>
> {code:java}
> 02-08 Jdbc(sql=[SELECT 1 "source_cnt", 0 "target_cnt", "SALE_ID", "PROD_ID", "CUST_ID", "TIME_ID", TRIM(BOTH ' ' FROM "CHANNEL_ID") "CHANNEL_ID", "PROMO_ID", "QUANTITY_SOLD", "AMOUNT_SOLD", "CREATEDDATE", "MODIFIEDDATE"
> FROM "FINAPP"."SALES"]) : rowType = RecordType(INTEGER source_cnt, INTEGER target_cnt, DECIMAL(0, 0) SALE_ID, DECIMAL(6, 0) PROD_ID, DECIMAL(0, 0) CUST_ID, TIMESTAMP(0) TIME_ID, VARCHAR(65535) CHANNEL_ID, DECIMAL(6, 0) PROMO_ID, DECIMAL(3, 0) QUANTITY_SOLD, DECIMAL(10, 2) AMOUNT_SOLD, TIMESTAMP(0) CREATEDDATE, TIMESTAMP(0) MODIFIEDDATE): rowcount = 100.0, cumulative cost = {100.0 rows, 100.0 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 4648
> {code}
> Below is the attached profile for your reference:
> [^23a59a1c-e0bb-d5d2-a686-8c4c9ddc6e0f.sys.drill]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)