drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-1577) Setting planner.width.max_per_node to use ALL the cores results in TPCH 4 failing with "Hash join does not support schema changes"
Date Sun, 04 Jan 2015 21:28:55 GMT

     [ https://issues.apache.org/jira/browse/DRILL-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacques Nadeau resolved DRILL-1577.
-----------------------------------
    Resolution: Fixed

> Setting planner.width.max_per_node to use ALL the cores results in TPCH 4 failing with
"Hash join does not support schema changes"
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-1577
>                 URL: https://issues.apache.org/jira/browse/DRILL-1577
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Metadata, Query Planning & Optimization
>    Affects Versions: 0.6.0
>         Environment: 10-node Drill cluster with TPCH schema (SF100)
> OS: RHEL 6.4
> cores/node: 32
> RAM: 256GB
>            Reporter: Kunal Khatua
>             Fix For: 0.8.0
>
>
> 0: jdbc:drill:schema=dfs.parquet> alter session set `planner.width.max_per_node`=31;
> +------------+------------+
> |     ok     |  summary   |
> +------------+------------+
> | true       | planner.width.max_per_node updated. |
> +------------+------------+
> 1 row selected (0.018 seconds)
> 0: jdbc:drill:schema=dfs.parquet> select o.o_orderpriority, count(*) as order_count
from orders_par100 o where o.o_orderdate >= date '1996-10-01' and o.o_orderdate < date
'1996-10-01' + interval '3' month and exists ( select * from lineitem_par100 l where l.l_orderkey
= o.o_orderkey and l.l_commitdate < l.l_receiptdate ) group by o.o_orderpriority order
by o.o_orderpriority;
> +-----------------+-------------+
> | o_orderpriority | order_count |
> +-----------------+-------------+
> | [B@2f943dc1     | 1052691     |
> | [B@2d62624e     | 1049305     |
> | [B@16240629     | 1053177     |
> | [B@1710791a     | 1053203     |
> | [B@3a7ea5ca     | 1053789     |
> +-----------------+-------------+
> 5 rows selected (23.918 seconds)
> 0: jdbc:drill:schema=dfs.parquet> alter session set `planner.width.max_per_node`=32;
> +------------+------------+
> |     ok     |  summary   |
> +------------+------------+
> | true       | planner.width.max_per_node updated. |
> +------------+------------+
> 1 row selected (0.019 seconds)
> 0: jdbc:drill:schema=dfs.parquet> select o.o_orderpriority, count(*) as order_count
from orders_par100 o where o.o_orderdate >= date '1996-10-01' and o.o_orderdate < date
'1996-10-01' + interval '3' month and exists ( select * from lineitem_par100 l where l.l_orderkey
= o.o_orderkey and l.l_commitdate < l.l_receiptdate ) group by o.o_orderpriority order
by o.o_orderpriority;
> Query failed: Failure while running fragment. Hash join does not support schema changes
[794badc9-a76f-468a-b3e6-6d2832aa1ecd]
> Error: exception while executing query: Failure while trying to get next result batch.
(state=,code=0)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message