You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kent Yao (Jira)" <ji...@apache.org> on 2026/03/28 03:24:00 UTC
[jira] [Resolved] (SPARK-56258) Make MetricUtils.stringValue lenient for unknown metric types
[ https://issues.apache.org/jira/browse/SPARK-56258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kent Yao resolved SPARK-56258.
------------------------------
Fix Version/s: 4.2.0
Resolution: Fixed
Issue resolved by pull request 55060
[https://github.com/apache/spark/pull/55060]
> Make MetricUtils.stringValue lenient for unknown metric types
> -------------------------------------------------------------
>
> Key: SPARK-56258
> URL: https://issues.apache.org/jira/browse/SPARK-56258
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.2.0
> Reporter: Kent Yao
> Assignee: Kent Yao
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.2.0
>
>
> MetricUtils.stringValue throws SparkException.internalError on unknown metric types, which is over-defensive for a UI rendering function. A crash at display time is worse than showing a degraded metric.
> Change to best-effort rendering: log at DEBUG level and format as '[unknown] N' with NumberFormat. This also enables downstream projects (Gluten, Comet) to define custom metric types without Spark core throwing.
--
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