[
https://issues.apache.org/jira/browse/FLINK-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426505#comment-15426505
]
ASF GitHub Bot commented on FLINK-4273:
---------------------------------------
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.
> Refactor JobClientActor to watch already submitted jobs
> --------------------------------------------------------
>
> Key: FLINK-4273
> URL: https://issues.apache.org/jira/browse/FLINK-4273
> Project: Flink
> Issue Type: Sub-task
> Components: Client
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 1.2.0
>
>
> The JobClientActor assumes that it receives a job, submits it, and waits for
> the result. This process should be broken up into a submission process and a
> waiting process which can both be entered independently. This leads to two
> different entry points:
> 1) submit(job) -> wait
> 2) retrieve(jobID) -> wait
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
