You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2016/06/23 23:23:16 UTC
[jira] [Resolved] (SPARK-16165) Fix the update logic for
InMemoryTableScanExec.readBatches accumulator
[ https://issues.apache.org/jira/browse/SPARK-16165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Lian resolved SPARK-16165.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
Issue resolved by pull request 13870
[https://github.com/apache/spark/pull/13870]
> Fix the update logic for InMemoryTableScanExec.readBatches accumulator
> ----------------------------------------------------------------------
>
> Key: SPARK-16165
> URL: https://issues.apache.org/jira/browse/SPARK-16165
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Dongjoon Hyun
> Assignee: Dongjoon Hyun
> Priority: Minor
> Fix For: 2.0.1, 2.1.0
>
>
> Currently, `readBatches` accumulator of `InMemoryTableScanExec` is updated only when `spark.sql.inMemoryColumnarStorage.partitionPruning` is true.
> Although this metric is used for only testing purpose, we had better have correct metric without considering SQL options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org