hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "liyunzhang (JIRA)" <>
Subject [jira] [Commented] (HIVE-18148) NPE in SparkDynamicPartitionPruningResolver
Date Wed, 13 Dec 2017 07:08:00 GMT


liyunzhang commented on HIVE-18148:

[~lirui]:  tried to use the example you provided.

set hive.spark.dynamic.partition.pruning=true;
explain select * from src join part1 on src.key=part1.p join part2 on src.value=part2.q;


But  in my env( latest build: 095e6bf8988a03875bc9340b2ab82d5d13c4cb3c), the physical plan
 before SparkCompiler#removeNestedDPP is 
there is no dpp operator for removeNestedDPP to traverse because HIVE-17087. SparkMapJoinOptimizer#convertJoinMapJoin
removes dpp operator when there is mapjoin operator.

So did you reproduce the NPE when setting  {{}} as
false?  BTW,  how does Hive on Tez deal with this kind of nested dpp case?

> NPE in SparkDynamicPartitionPruningResolver
> -------------------------------------------
>                 Key: HIVE-18148
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Spark
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-18148.1.patch
> The stack trace is:
> {noformat}
> 2017-11-27T10:32:38,752 ERROR [e6c8aab5-ddd2-461d-b185-a7597c3e7519 main] ql.Driver:
FAILED: NullPointerException null
> java.lang.NullPointerException
>         at org.apache.hadoop.hive.ql.optimizer.physical.SparkDynamicPartitionPruningResolver$SparkDynamicPartitionPruningDispatcher.dispatch(
>         at org.apache.hadoop.hive.ql.lib.TaskGraphWalker.dispatch(
>         at org.apache.hadoop.hive.ql.lib.TaskGraphWalker.walk(
>         at org.apache.hadoop.hive.ql.lib.TaskGraphWalker.startWalking(
>         at org.apache.hadoop.hive.ql.optimizer.physical.SparkDynamicPartitionPruningResolver.resolve(
>         at org.apache.hadoop.hive.ql.parse.spark.SparkCompiler.optimizeTaskPlan(
> {noformat}
> At this stage, there shouldn't be a DPP sink whose target map work is null. The root
cause seems to be a malformed operator tree generated by SplitOpTreeForDPP.

This message was sent by Atlassian JIRA

View raw message