[
https://issues.apache.org/jira/browse/HIVE-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497788#comment-13497788
]
Namit Jain commented on HIVE-3706:
----------------------------------
Running tests - will commit if tests pass.
Ideally, checks like this should be part of plan, and we should not look at the
conf. at runtime.
This will make the explain plan be able to log these values.
However, this is outside the scope of this task, and can be performed in a
follow-up.
> getBoolVar in FileSinkOperator can be optimized
> -----------------------------------------------
>
> Key: HIVE-3706
> URL: https://issues.apache.org/jira/browse/HIVE-3706
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Affects Versions: 0.10.0
> Reporter: Kevin Wilfong
> Assignee: Kevin Wilfong
> Attachments: HIVE-3706.1.patch.txt
>
>
> There's a call to HiveConf.getBoolVar in FileSinkOperator's processOp method.
> In benchmarks we found this call to be using ~2% of the CPU time on simple
> queries, e.g. INSERT OVERWRITE TABLE t1 SELECT * FROM t2;
> This boolean value, a flag to collect the RawDataSize stat, won't change
> during the processing of a query, so we can determine it at initialization
> and store that value, saving that CPU.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
