[
https://issues.apache.org/jira/browse/FLINK-14992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986569#comment-16986569
]
Zili Chen commented on FLINK-14992:
-----------------------------------
I notice that unless we port {{(Local|Remote)Environment}} to use new
{{Executor}} we can hardly make {{JobListener}} work in every case. We're able
to easily add a {{JobListener}} list in Environment and call it on
{{JobClient}} Future gotten. However, it doesn't work in codepath where
{{execute}} is hijacked and never calls {{super.execute}}.
> Add job submission listener to execution environments
> -----------------------------------------------------
>
> Key: FLINK-14992
> URL: https://issues.apache.org/jira/browse/FLINK-14992
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataSet, API / DataStream
> Reporter: Aljoscha Krettek
> Priority: Major
> Fix For: 1.10.0
>
>
> We should add a way of registering listeners that are notified when a job is
> submitted for execution using an environment. This is useful for cases where
> a framework, for example the Zeppelin Notebook, creates an environment for
> the user, the user can submit jobs, but the framework needs a handle to the
> job in order to manage it.
> This can be as simple as
> {code}
> interface JobSubmissionListener {
> void notify(JobClient jobClient)
> }
> {code}
> with a method {{registerJobSubmissionListener(JobSubmissionListener)}} on the
> environments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
