[jira] [Resolved] (SPARK-41442) Only update SQLMetric value if merging with valid metric

["Dongjoon Hyun (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-41442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun resolved SPARK-41442.
-----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

Issue resolved by pull request 38969
[https://github.com/apache/spark/pull/38969]

> Only update SQLMetric value if merging with valid metric
> --------------------------------------------------------
>
>                 Key: SPARK-41442
>                 URL: https://issues.apache.org/jira/browse/SPARK-41442
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.4.0
>            Reporter: L. C. Hsieh
>            Assignee: L. C. Hsieh
>            Priority: Minor
>             Fix For: 3.4.0
>
>
> We use -1 as initial value of SQLMetric, and change it to 0 while merging with other SQLMetric instances. A SQLMetric will be treated as invalid and filtered out later.
> While we are developing with Spark, it is trouble behavior that two invalid SQLMetric instances merge to a valid SQLMetric because merging will set the value to 0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org