You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Panagiotis Garefalakis (Jira)" <ji...@apache.org> on 2023/05/17 03:45:00 UTC

[jira] [Updated] (FLINK-32114) Make FailureEnricherContext more flexible and include task specific fields

     [ https://issues.apache.org/jira/browse/FLINK-32114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Panagiotis Garefalakis updated FLINK-32114:
-------------------------------------------
    Summary: Make FailureEnricherContext more flexible and include task specific fields  (was: Extend FailureEnricherContext with task specific fields)

> Make FailureEnricherContext more flexible and include task specific fields
> --------------------------------------------------------------------------
>
>                 Key: FLINK-32114
>                 URL: https://issues.apache.org/jira/browse/FLINK-32114
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Panagiotis Garefalakis
>            Priority: Major
>
> On task failures, context would be nice to include extra fields like taskName, location, etc.
> Discussion under: [https://github.com/apache/flink/pull/22506#discussion_r1195408929]
> We may need to provide more information about the error to the enrichers, e.g. related task. Such information can be decided only after an error occurs. So maybe a more flexible way is to create a new context for each failure dynamically, i.e. create from {{failedExecution }} in {{{}handleFailure (){}}}.
> [https://github.com/apache/flink/pull/22506#discussion_r1195539179]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)