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 08:45:00 UTC

[GitHub] [flink] aljoscha commented on issue #10408: [FLINK-14992][client] Add job listener to execution environments

aljoscha commented on issue #10408: [FLINK-14992][client] Add job listener to execution environments
URL: https://github.com/apache/flink/pull/10408#issuecomment-561537390
 
 
   @kl0u Had a good idea: We think that the lifecycle of the client that is given to the listener has to be completely separate. We can do this by adding a `clone()` or `duplicate()` method to `ClusterClient`, which creates a new copy that has deep copies of all the required resources. Then we can add a `JobClient.duplicate()` which does the same for the `JobClient`. This way, the listener and the user (on the return value of `executeAsync()`) can do whatever they want with the client. What do you think?

----------------------------------------------------------------
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