You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2018/06/15 16:59:00 UTC
[jira] [Commented] (HIVE-19912) Schema evolution checks prints a
log line in INFO mode for each vectorized rowbatch, impacts performance
[ https://issues.apache.org/jira/browse/HIVE-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514095#comment-16514095 ]
Prasanth Jayachandran commented on HIVE-19912:
----------------------------------------------
LOG.isInfoEnabled() -> LOG.isDebugEnabled() ?
> Schema evolution checks prints a log line in INFO mode for each vectorized rowbatch, impacts performance
> --------------------------------------------------------------------------------------------------------
>
> Key: HIVE-19912
> URL: https://issues.apache.org/jira/browse/HIVE-19912
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 3.0.0
> Reporter: Nita Dembla
> Assignee: Nita Dembla
> Priority: Major
> Fix For: 3.0.1
>
> Attachments: HIVE-19912.1.patch
>
>
> While benchmarking query96, noticed 17K log lines printed for each vector rowbactch
>
> In file ql/src/java/org/apache/hadoop/hive/ql/io/orc/OrcInputFormat.java
>
> {code:java}
> @@ -2554,8 +2554,8 @@ public static TypeDescription getDesiredRowTypeDescr(Configuration conf,
> }
> if (haveSchemaEvolutionProperties) {
> - if (LOG.isInfoEnabled()) {
> - LOG.info("Using schema evolution configuration variables schema.evolution.columns " +
> + if (LOG.isDebugEnabled()) {
> + LOG.debug("Using schema evolution configuration variables schema.evolution.columns " +
> schemaEvolutionColumnNames.toString() +
> " / schema.evolution.columns.types " +
> schemaEvolutionTypeDescrs.toString() +{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)