hive-issues mailing list archives

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


Rui Li commented on HIVE-18148:

[~kellyzly], I think you can try disabling map join. Or you can just run the new test with
master branch and it should fail - let me know if it doesn't.
I haven't looked into tez but my guess is it won't be a problem, because tez doesn't require
extra jobs to evaluate DPP sinks. But for spark, some work is computed multiple times in order
to support DPP. And that's why I prefer to avoid such 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