You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Rui Li (JIRA)" <ji...@apache.org> on 2017/11/21 03:53:01 UTC
[jira] [Updated] (HIVE-18111) Fix temp path for Spark DPP sink
[ https://issues.apache.org/jira/browse/HIVE-18111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rui Li updated HIVE-18111:
--------------------------
Description:
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}}.
> Fix temp path for Spark DPP sink
> --------------------------------
>
> Key: HIVE-18111
> URL: https://issues.apache.org/jira/browse/HIVE-18111
> Project: Hive
> Issue Type: Bug
> Reporter: Rui Li
> Assignee: Rui Li
>
> 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
(v6.4.14#64029)