You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2022/12/29 00:05:00 UTC
[jira] [Resolved] (SPARK-41533) GRPC Errors on the client should be cleaned up
[ https://issues.apache.org/jira/browse/SPARK-41533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-41533.
----------------------------------
Fix Version/s: 3.4.0
Resolution: Fixed
Issue resolved by pull request 39212
[https://github.com/apache/spark/pull/39212]
> GRPC Errors on the client should be cleaned up
> ----------------------------------------------
>
> Key: SPARK-41533
> URL: https://issues.apache.org/jira/browse/SPARK-41533
> Project: Spark
> Issue Type: Sub-task
> Components: Connect
> Affects Versions: 3.4.0
> Reporter: Martin Grund
> Assignee: Martin Grund
> Priority: Major
> Fix For: 3.4.0
>
>
> When the server throws an exception we report a very deep stack trace that is not helpful for the user.
> We need to separate the cause from the user visible exception and wrap the error into custom exception instead of publishing the RPCError from GRPC
--
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