[
https://issues.apache.org/jira/browse/SPARK-43482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-43482.
----------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
Issue resolved by pull request 41150
[https://github.com/apache/spark/pull/41150]
> Expand QueryTerminatedEvent to contain error class if it exists in exception
> ----------------------------------------------------------------------------
>
> Key: SPARK-43482
> URL: https://issues.apache.org/jira/browse/SPARK-43482
> Project: Spark
> Issue Type: Task
> Components: Structured Streaming
> Affects Versions: 3.5.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Major
> Fix For: 3.5.0
>
>
> As of now, the event QueryTerminatedEvent has a field about exception which
> is just a string representation of underlying exception, mostly stack trace.
> That said, people relying on streaming query listener can't get any benefit
> from the movement for employing error class framework. This is a bad
> observability once we migrate exceptions in streaming query to error class
> framework where exceptions are well categorized.
> We can expand the event of QueryTerminatedEvent - if the exception contains
> error class information, we can ship this along with existing string version
> of exception (message).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
