[
https://issues.apache.org/jira/browse/SPARK-26327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717592#comment-16717592
]
ASF GitHub Bot commented on SPARK-26327:
----------------------------------------
SparkQA removed a comment on issue #23287: [SPARK-26327][SQL][BACKPORT-2.4] Bug
fix for `FileSourceScanExec` metrics update
URL: https://github.com/apache/spark/pull/23287#issuecomment-446202597
**[Test build #99976 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/99976/testReport)**
for PR 23287 at commit
[`368c7b5`](https://github.com/apache/spark/commit/368c7b50cbbb18b4dd6b11d6d4791448a057ffc3).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Metrics in FileSourceScanExec not update correctly while
> relation.partitionSchema is set
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-26327
> URL: https://issues.apache.org/jira/browse/SPARK-26327
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Yuanjian Li
> Assignee: Yuanjian Li
> Priority: Major
> Fix For: 3.0.0
>
>
> As currently approach in `FileSourceScanExec`, the metrics of "numFiles" and
> "metadataTime"(fileListingTime) were updated while lazy val
> `selectedPartitions` initialized in the scenario of relation.partitionSchema
> is set. But `selectedPartitions` will be initialized by `metadata` at first,
> which is called by `queryExecution.toString` in
> `SQLExecution.withNewExecutionId`. So while the
> `SQLMetrics.postDriverMetricUpdates` called, there's no corresponding
> liveExecutions in SQLAppStatusListener, the metrics update is not work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
