Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1176
@Leemoonsoo
Thank you for your opinion!
#### Workflow definition
I actually agree with your opinion.
The reason I made <dynamic form> is thought that the user wants to manage
the workflow Note.
I am satisfied with the usability of the workflow according to the <dynamic
form>.
However, there was doubt whether this is also no problem using the <dynamic
form>.
It is not consistent usage.
Maybe @corneadoug think is right.
(add workflow feature in job menu)
Also feel the need to do to represent the workflow Paragraph well.
<% Workflow> are a good idea.
However, it is creating a new interpreter makes a number of concerns.
Maybe <Dynamic Form> is the same problem with this issue with.
This part I will try to think more.
#### Alternative approach
I know of the existence of z.run.
However, z.run can not replace this function.
z.run does not guarantee the order of execution of each other for the other
Paragraph interpreter.
Case 2 See the following image.
Thanks again for details opinion.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
