Thanks for the clarification.
On Tue, May 23, 2023 at 7:07 PM Weihua Hu wrote:
> Hi Sharif,
>
> You could not catch exceptions globally.
>
> For exceptions that can be explicitly ignored for your business, you need
> to add a try-catch in the operators.
> For exceptions that are not catched, Fli
Hi Sharif,
You could not catch exceptions globally.
For exceptions that can be explicitly ignored for your business, you need
to add a try-catch in the operators.
For exceptions that are not catched, Flink will trigger a recovery from
failure automatically[1].
[1]
https://nightlies.apache.org/fl
Thanks for your response.
For simplicity, I want to capture exceptions in a centralized manner and
log them for further analysis, without interrupting the job's execution or
causing it to restart.
On Tue, May 23, 2023 at 6:31 AM Shammon FY wrote:
> Hi Sharif,
>
> I would like to know what do yo
Hi Sharif,
I would like to know what do you want to do with the exception after
catching it? There are different ways for different requirements, for
example, Flink has already reported these exceptions.
Best,
Shammon FY
On Mon, May 22, 2023 at 4:45 PM Sharif Khan via user
wrote:
> Hi, commun
Hi, community.
Can anyone please let me know?
1. What is the best practice in terms of handling exceptions in Flink jobs?
2. Is there any way to catch exceptions globally in Flink jobs? Basically,
I want to catch exceptions from any operators in one place (globally).
my expectation is let's say
