aljoscha commented on issue #10408: [FLINK-14992][client] Add job listener to execution environments URL: https://github.com/apache/flink/pull/10408#issuecomment-562214822 But if the listener just gets the same `JobClient` that the user gets as a return value of `executeAsync()`, you can never know when that might be closed. If you need to store that client in Zeppelin it might just be closed and you can't use it. Wouldn't it be easier if Zeppelin had a `JobClient` where it controls the lifecycle of the `JobClient` and not depend on the user not to close the `JobClient`?
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
