[
https://issues.apache.org/jira/browse/KAFKA-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-13381.
--------------------------------------------
Resolution: Fixed
> Wrap all uncaught exceptions as StreamsException with TaskId field
> ------------------------------------------------------------------
>
> Key: KAFKA-13381
> URL: https://issues.apache.org/jira/browse/KAFKA-13381
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Assignee: A. Sophie Blee-Goldman
> Priority: Major
> Labels: kip
> Fix For: 3.1.0
>
>
> KIP-783:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-783%3A+Add+TaskId+field+to+StreamsException]
>
> Currently only some exceptions that occur during processing are wrapped as a
> StreamsException, which complicates the logic required by a user custom
> StreamsUncaughtExceptionHandler. It would be cleaner to ensure that all
> exceptions thrown to the user/handler are wrapped (exactly once) as a
> StreamsException.
> Further, many exceptions can be traced back to a particular task: eg due to a
> timeout of that task, or thrown during Task#process, or while
> closing/suspending/etc that task. It can be helpful both to debugging as well
> as to handling to have that information, so we can add a TaskId field to the
> StreamsException class to help users identify the source of an exception
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
