Khurram Faraaz created DRILL-6453:
-------------------------------------
Summary: TPC-DS query 72 has regressed
Key: DRILL-6453
URL: https://issues.apache.org/jira/browse/DRILL-6453
Project: Apache Drill
Issue Type: Bug
Components: Execution - Flow
Affects Versions: 1.14.0
Reporter: Khurram Faraaz
Attachments: 24f75b18-014a-fb58-21d2-baeab5c3352c.sys.drill
TPC-DS query 72 seems to have regressed, query profile for the case where it
Canceled after 2 hours on Drill 1.14.0 is attached here.
{noformat}
On, Drill 1.14.0-SNAPSHOT
commit : 931b43e (TPC-DS query 72 executed successfully on this commit, took
around 55 seconds to execute)
SF1 parquet data on 4 nodes;
planner.memory.max_query_memory_per_node = 10737418240.
drill.exec.hashagg.fallback.enabled = true
TPC-DS query 72 executed successfully & took 47 seconds to complete execution.
{noformat}
{noformat}
TPC-DS data in the below run has date values stored as DATE datatype and not
VARCHAR type
On, Drill 1.14.0-SNAPSHOT
commit : 82e1a12
SF1 parquet data on 4 nodes;
planner.memory.max_query_memory_per_node = 10737418240.
drill.exec.hashagg.fallback.enabled = true
and
alter system set `exec.hashjoin.num_partitions` = 1;
TPC-DS query 72 executed for 2 hrs and 11 mins and did not complete, I had to
Cancel it by stopping the Foreman drillbit.
As a result several minor fragments are reported to be in
CANCELLATION_REQUESTED state on UI.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
