Marko Sisovic created SPARK-61649:
-------------------------------------

             Summary: Preserve structured JVM linkage error details
                 Key: SPARK-61649
                 URL: https://issues.apache.org/jira/browse/SPARK-61649
             Project: Spark
          Issue Type: Bug
          Components: Connect
    Affects Versions: 5.0.0
            Reporter: Marko Sisovic


Spark Connect handles LinkageError subclasses outside the structured error path 
because Scala NonFatal excludes them. NoClassDefFoundError, 
ExceptionInInitializerError, and NoSuchMethodError therefore produce a generic 
UNKNOWN gRPC response without an error ID, preventing clients from fetching JVM 
stack traces and cause chains. ExceptionInInitializerError can also have a null 
message, which the protobuf setter rejects.

Handle LinkageError through the existing structured error path and serialize 
null messages as empty strings. Add regression coverage for these three error 
types.

PR: https://github.com/apache/spark/pull/60454



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to