[jira] [Resolved] (SPARK-56926) Guard against null messageParameters in Connect error proto serialization

["Ruifeng Zheng (Jira)" <ji...@apache.org>]

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

Ruifeng Zheng resolved SPARK-56926.
-----------------------------------
    Fix Version/s: 4.3.0
       Resolution: Fixed

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

> Guard against null messageParameters in Connect error proto serialization
> -------------------------------------------------------------------------
>
>                 Key: SPARK-56926
>                 URL: https://issues.apache.org/jira/browse/SPARK-56926
>             Project: Spark
>          Issue Type: Bug
>          Components: Connect
>    Affects Versions: 4.0.0, 5.0.0
>            Reporter: Haoyan Geng
>            Assignee: Haoyan Geng
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.3.0
>
>
> In ErrorUtils.throwableToProtoErrors (Spark Connect server), the call sparkThrowableBuilder.putAllMessageParameters(sparkThrowable.getMessageParameters) is unguarded. If a SparkThrowable implementation returns null from getMessageParameters() (violating the implicit non-null contract of the interface's default), putAllMessageParameters(null) throws a NullPointerException and crashes the FetchErrorDetails RPC.
> When this happens, the client falls back to a degraded error reconstruction that drops the cause chain, hiding the underlying error from the user.



--
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