[
https://issues.apache.org/jira/browse/SPARK-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325406#comment-14325406
]
Apache Spark commented on SPARK-5880:
-------------------------------------
User 'nitin2goyal' has created a pull request for this issue:
https://github.com/apache/spark/pull/4669
> Change log level of batch pruning string in InMemoryColumnarTableScan from
> Info to Debug
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-5880
> URL: https://issues.apache.org/jira/browse/SPARK-5880
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.3.0, 1.2.1
> Reporter: Nitin Goyal
> Priority: Trivial
> Fix For: 1.3.0
>
>
> In InMemoryColumnarTableScan, we make string of the statistics of all the
> columns and log them at INFO level whenever batch pruning happens. We get a
> performance hit in case there are a large number of batches and good number
> of columns and almost every batch gets pruned.
> We can make the string to evaluate lazily and change log level to DEBUG
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
