CheneyYin opened a new issue, #6064: URL: https://github.com/apache/seatunnel/issues/6064
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened In the `seatunnel-formats` module, some serialization classes control whether exceptions are passed according to `ignoreParseErrors`. https://github.com/apache/seatunnel/blob/2c5b48e9078718cb31464e850f2a62da137c8b4d/seatunnel-formats/seatunnel-format-json/src/main/java/org/apache/seatunnel/format/json/JsonDeserializationSchema.java#L129-L141 Some code blocks use `try {...} catch (Throwable t) {...}` to handle exceptions, similar to the above. However, `catch Throwable` is too broad. Even with `ignoreParseErrors` enabled, I prefer not to ignore errors like OutOfMemoryError or StackOverflowError. ### SeaTunnel Version dev ### SeaTunnel Config ```conf none ``` ### Running Command ```shell none ``` ### Error Exception ```log none ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
