hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <>
Subject [jira] [Commented] (HIVE-18111) Fix temp path for Spark DPP sink
Date Tue, 12 Dec 2017 18:05:00 GMT


Sahil Takiar commented on HIVE-18111:

+1 assuming Hive QA failures are benign, there is also a checkstyle issue that should be fixed

One more question, if each DPP work outputs to {{QUERY_TMP_PATH/dpp_output/dppWorkId}}. And
each map work reads from {{QUERY_TMP_PATH/dpp_output}}, what happens if there are multiple
DPP sinks within a query with different target map works.

> Fix temp path for Spark DPP sink
> --------------------------------
>                 Key: HIVE-18111
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Spark
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-18111.1.patch, HIVE-18111.2.patch, HIVE-18111.3.patch, HIVE-18111.4.patch,
HIVE-18111.5.patch, HIVE-18111.5.patch
> Before HIVE-17877, each DPP sink has only one target work. The output path of a DPP work
is {{TMP_PATH/targetWorkId/dppWorkId}}. When we do the pruning, each map work reads DPP outputs
under {{TMP_PATH/targetWorkId}}.
> After HIVE-17877, each DPP sink can have multiple target works. It's possible that a
map work needs to read DPP outputs from multiple {{TMP_PATH/targetWorkId}}. To solve this,
I think we can have a DPP output path specific to each query, e.g. {{QUERY_TMP_PATH/dpp_output}}.
Each DPP work outputs to {{QUERY_TMP_PATH/dpp_output/dppWorkId}}. And each map work reads
from {{QUERY_TMP_PATH/dpp_output}}.

This message was sent by Atlassian JIRA

View raw message