exceptionfactory commented on PR #10455: URL: https://github.com/apache/nifi/pull/10455#issuecomment-3452695947
> I chose the `ExecuterService` approach because the `getGroovyScript` method can return checked exceptions that the validation relies on, so using Futures seemed like a cleaner solution then going with implementing an `UncaughtExceptionHandler`. Should I make the `ExecutionService` reusable to save on resources? Thanks for explanation. Declaring the `ExecutorService` as an instance variable could be an option, although some lifecycle management would be involved. To handle exceptions, calling `getGroovyScript()` in a try-catch with `Throwable` should avoid uncaught exceptions. -- 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]
