You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/12/04 02:13:48 UTC
[GitHub] [flink] TisonKun commented on issue #10408: [FLINK-14992][client]
Add job listener to execution environments
TisonKun commented on issue #10408: [FLINK-14992][client] Add job listener to execution environments
URL: https://github.com/apache/flink/pull/10408#issuecomment-561443882
In my opinion such JobListener is mainly used by job management platform such as Zeppelin which is only interested in which job has been submitted. It's a user behavior what to communicate with the job. If one want to communicate with the job "on job submitted", he can get the `JobClient` from `executeAsync` and do anything he wants to do and close the job client when done. A daemon listener should not communicate with the job. Is it Zeppelin case? @zjffdu
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services