Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2313
Good work @mxm. I made some minor comments inline.
Just for my own clarification: Is it still planned to have a new kind of
`JobClient` which is bound to a specific job and which can be used to issue job
specific calls such as `cancel`, `stop`, execution result retrieval, etc. I
thought that the `ClusterClient` is used to communicate with the cluster,
whereas the `JobClient` is responsible for the job communication. Will this be
a follow-up?
The test case `JobClientActorTest.
testConnectionTimeoutAfterJobRegistration` is failing on Travis.
After addressing the comments +1 for merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
