[
https://issues.apache.org/jira/browse/HIVE-9128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249209#comment-14249209
]
Brock Noland commented on HIVE-9128:
------------------------------------
Agreed that a second isn't very helpful for our use case. Perhaps we'll hold
off on this one for now.
> 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)
