You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2023/01/13 18:09:00 UTC
[jira] [Commented] (SPARK-42057) Avoid losing exception info in Protobuf errors
[ https://issues.apache.org/jira/browse/SPARK-42057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676722#comment-17676722 ]
Apache Spark commented on SPARK-42057:
--------------------------------------
User 'rangadi' has created a pull request for this issue:
https://github.com/apache/spark/pull/39536
> Avoid losing exception info in Protobuf errors
> ----------------------------------------------
>
> Key: SPARK-42057
> URL: https://issues.apache.org/jira/browse/SPARK-42057
> Project: Spark
> Issue Type: Bug
> Components: Protobuf
> Affects Versions: 3.4.0
> Reporter: Raghu Angadi
> Priority: Major
> Fix For: 3.4.0
>
>
> Protobuf connector related error handlers incorrectly report the exception. This is makes it hard for users to see actual issue. E.g. if there is a {{FileNotFoundException}} these error handlers use pass {{exception.getCause()}} rather than passing {{{}exception{}}}. As result, we lose the information that it was a {{FileNotFoundException}}
--
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