You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2014/12/17 00:52:15 UTC

[jira] [Updated] (HIVE-9128) Evaluate hive.rpc.query.plan performance [Spark Branch]

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

Brock Noland updated HIVE-9128:
-------------------------------
    Parent Issue: HIVE-9134  (was: HIVE-7292)

> Evaluate hive.rpc.query.plan performance [Spark Branch]
> -------------------------------------------------------
>
>                 Key: HIVE-9128
>                 URL: https://issues.apache.org/jira/browse/HIVE-9128
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Brock Noland
>            Assignee: Jimmy Xiang
>
> Tez uses [hive.rpc.query.plan|https://github.com/apache/hive/blob/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java#L1874] which is used in {{Utilities.java}}. Basically instead of writing the query plan to HDFS, the query plan is placed in the JobConf object and then de-serialized form there.
> We should do some evaluation to see which is more performant for us. We might need to place some timings in {{Utilities}} to understand this if the PerfLog doesn't have enough information today.



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