[
https://issues.apache.org/jira/browse/FLINK-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991625#comment-16991625
]
Jeff Zhang commented on FLINK-15157:
------------------------------------
[~aljoscha] [~kkl0u] This is how I use it in Zeppelin
https://github.com/zjffdu/zeppelin/blob/flink_1.10_emr/flink/src/main/scala/org/apache/zeppelin/flink/FlinkScalaInterpreter.scala
Actually I use it very similar as flink scala shell, I just start a flink scala
shell as a long running service which will accept requests from external world
(web browser), and then run the code and response with the code execution
result. So basically I need to 2 main things
1. Manage the lifecycle of flink cluster. Create/destroy the flink cluster no
matter it is local MIniCluster or yarn FlinkCluster.
2. Manage the lifecycle of flink job, Add hooks to the lifecycle of flink job
so that I can get more job info during its execution, such as its flink job web
url, job progress and etc.
> Make ScalaShell ensureYarnConfig() and fetchConnectionInfo() public
> -------------------------------------------------------------------
>
> Key: FLINK-15157
> URL: https://issues.apache.org/jira/browse/FLINK-15157
> Project: Flink
> Issue Type: Bug
> Components: Scala Shell
> Reporter: Aljoscha Krettek
> Priority: Major
>
> This allows users of the Scala Shell, such as Zeppelin to work better with
> the shell.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
