Hi Scott, IMHO, the exception is caused by the user codes so it should be handled by the user function, and Flink runtime shouldn’t make any assumption about what’s happening in the user function.
The exception may or may not be caused by unexpected data, so logging the current processing records is not always helpful. What do you think? Best, Paul Lam > 在 2018年11月22日，13:20，Scott Sue <scott....@celer-tech.com> 写道： > > Hi Paul, > > Thanks for the quick reply. Ok does that mean that as general practice, I > should be catching all exceptions for the purpose of logging in any of my > Operators? This seems like something that could be handled by Flink itself > as they are unexpected exceptions. Otherwise every single operator I create > must have a try catch block? > > > Regards, > Scott > > SCOTT SUE > CHIEF TECHNOLOGY OFFICER > > Support Line : +44(0) 2031 371 603 > Mobile : +852 9611 3969 > > 9/F, 33 Lockhart Road, Wan Chai, Hong Kong > www.celer-tech.com <http://www.celer-tech.com/> > > > > > > >> On 22 Nov 2018, at 13:17, Paul Lam <paullin3...@gmail.com >> <mailto:paullin3...@gmail.com>> wrote: >> >> ng the exception in the user function and log the current >> message that the operator is processing before re-throwing (or not) the >> exception to > > > This message, including any attachments, may include private, privileged and > confidential information and is intended only for the personal and > confidential use of the intended recipient(s). If the reader of this message > is not an intended recipient, you are hereby notified that any review, use, > dissemination, distribution, printing or copying of this message or its > contents is strictly prohibited and may be unlawful. If you are not an > intended recipient or have received this communication in error, please > immediately notify the sender by telephone and/or a reply email and > permanently delete the original message, including any attachments, without > making a copy.
