GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1176
[Zeppelin 1165 : improve] Paragraph dynamic relationship executable form
### What is this PR for?
Workflow process feature.
(To ensure the success of each paragraph, it is possible to run
consecutively.)
#### Case 1
Through a dynamic form, you can execute the order in paragraph.
There is a difference with traditional methods.
Please check the following flowchart.
#### Case 2
In general, when run a plurality of Paragraph, it performs Note entire run.
This is a good way to run a lot of Paragraph contained in the Note.
However, the problem occurs if the Interpreter of Paragraph different.
For Paragraph each using a different type of one of the Interpreter Note
but run in sequence, the end is all different.
For example, Markdown is a very fast Interpreter.
The process is completed very quickly.
This is a problem in the sequential execution Paragraph.
This feature ensures a certain execution order Notebook with each
Interpreter.
##### Case 3
For concurrent job in the workflow ...
If the current functional design is supposed to run at the same time, as
follows
It is to share the results of the job.
But if the situation need to run the job at the same time, subject to their
execution flow.
** The results will have to succeed, the following paragraph will be
executed. **
### What type of PR is it?
Improvement
### jira
https://issues.apache.org/jira/browse/ZEPPELIN-1165
### How should this be tested?
Dynamic form
For usage, see the following:
https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/manual/dynamicform.html
In the markdown type:
```
%md
${workflow:workflow=MyWorkflowName,NotebookId01:ParagraphId01|NotebookId02:ParagraphId02}
```
- details explain.
You can specify the title work flow.
Simply displayed on the UI.
```
${workflow:workflow=
or
${workflow:workflow=MyWorkflow
```
title name : MyWorkflow
character a comma(,), you can start working set.
```
${workflow:workflow=MyWorkflow**,**
```
Enter your Notebook ID and Paragraph ID.
```
${workflow:workflow=MyWorkflow,2BS99R6QA:20160712-163556_1475991024}
```
In order to distinguish between the Notebook ID and Paragraph ID,
characters <:> it is.
The example was set to run 20160712-163556_1475991024 paragraph with a
notebook id called 2BS99R6QA.
- how to get notebook id?
<img width="534" alt="getnotebookid"
src="https://cloud.githubusercontent.com/assets/10525473/16795411/30faab1c-4918-11e6-8ef3-8b6fc6f6f039.png";>
- how to get paragraph id?
<img width="810" alt="getparagraphid"
src="https://cloud.githubusercontent.com/assets/10525473/16795412/31041d8c-4918-11e6-9b9f-8f472692e3e1.png";>
Through a pipe character( | ), you can add tasks consecutively.
```
${workflow:workflow=MyWorkflow,2BS99R6QA:20160712-163556_1475991024|2BS99R6QA:20160710-03221_12234323}
```
#### Note run
If you want to run to all Paragraph in Note, you can:
```
NoteID : *
or
NoteID
```
```
${workflow:workflow=MyworkflowName,NotebookId}
or
${workflow:workflow=MyworkflowName,NotebookId:*}
```
for example
```
${workflow:workflow=Myworkflow,2A94M5J1Z}
```
Of course, it is possible to run a particular paragraph and mix.
```
%md
${workflow:workflow=Myworkflow,2A94M5J1Z|r|2BQWXDH1C:20160714-151024_1284650101}
```
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes, After the merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin
ZEPPELIN-1165-paragraph-relation-execution
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1176.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1176
----
commit 0d420ab3bc4576b6e9b5d770675f11b69ce4a8d2
Author: CloverHearts <[email protected]>
Date: 2016-07-13T06:27:59Z
implement backend for relation execution paragraph.
commit ff37526150ce7590c809bbb21285045f7ea98cb4
Author: CloverHearts <[email protected]>
Date: 2016-07-13T06:40:46Z
Implement frontend for relation execution paragraph
commit 8acab2eccd490141b6c9565fbe37214cf5b9dc02
Author: CloverHearts <[email protected]>
Date: 2016-07-13T06:43:19Z
remove log for devleop
commit 74affd8ea184c51c12079419cd07d53df2a6bcfb
Author: CloverHearts <[email protected]>
Date: 2016-07-14T01:04:54Z
Merge branch 'master' into ZEPPELIN-1165-paragraph-relation-execution
commit de5519f6cd544589355e6b1405a38f46615505ea
Author: CloverHearts <[email protected]>
Date: 2016-07-14T02:29:11Z
add featrue support all paragraph in note to run - front web
commit 2e9fe6c15c0308a4c9062da186a98cfe1256e215
Author: CloverHearts <[email protected]>
Date: 2016-07-14T03:40:19Z
support all run paragraph for workflow (implement backend)
----
---
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.
---
![https://cloud.githubusercontent.com/assets/10525473/16795411/30faab1c-4918-11e6-8ef3-8b6fc6f6f039.png"](https://cloud.githubusercontent.com/assets/10525473/16795411/30faab1c-4918-11e6-8ef3-8b6fc6f6f039.png"){kind=link}
![https://cloud.githubusercontent.com/assets/10525473/16795412/31041d8c-4918-11e6-9b9f-8f472692e3e1.png"](https://cloud.githubusercontent.com/assets/10525473/16795412/31041d8c-4918-11e6-9b9f-8f472692e3e1.png"){kind=link}
