Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@zjffdu
Thank you for your best advice!! :)
and Sorry, I missing the description.
actually, i made that on codebase. (dynamic form is removed.)
In fact, this feature has a dependency on Spark.
However, it is designed to be easily re-implemented in other interpreters.
There are also advantages.
Since calls can be made at any time in the code, we can use them together
during analysis or in combination with external libraries.
(DAG is the same)
By default, this is not a complete implementation of the workflow.
However, I think this feature provides the basic user environment for the
user to use freely.
```
if (z.getZeppelinJobStatus("execute note id", "execute paragraph
id").getJobStatus().isFinished() == true)
{ z.run("execute note id", "execute paragraph id") }
```
or
```
val result = z.runSync("execute note id", "execute paragraph id")
if (result.isFinished == true)
{ println("job is done") }
```
or
```
z.run("execute note id", "execute paragraph id")
while (z.getZeppelinJobStatus("execute note id", "execute paragraph
id").getJobStatus().isRunning)
{ // loop }
println("next job or done.");
```
---
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.
---
