GitHub user cloverhearts opened a pull request:

    https://github.com/apache/zeppelin/pull/1799

    [ZEPPELIN-1165 : WIP] Code-based job workflow

    ### What is this PR for?
    
    Code based workflow (**work in progress**)
    
    Re-implementation on this pr
    https://github.com/apache/zeppelin/pull/1176
    
    
    
    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.
    
![workflowdynamicformcontrol](https://cloud.githubusercontent.com/assets/10525473/16791726/a4b96ff0-48fc-11e6-8e23-9ec577066bb7.png)
    #### 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.
    
![notebook_example](https://cloud.githubusercontent.com/assets/10525473/16803203/175ad01a-4940-11e6-8949-72d0c49bdf9e.png)
    For Paragraph each using a different type of one of the Interpreter Note 
but run in sequence, the end is all different.
    
    ![normal notebook 
run](https://cloud.githubusercontent.com/assets/10525473/16803193/069c4d94-4940-11e6-9293-888b6c6288a0.png)
    For example, Markdown is a very fast Interpreter.
    The process is completed very quickly.
    This is a problem in the sequential execution Paragraph.
    
    ![worklfow 
run](https://cloud.githubusercontent.com/assets/10525473/16803192/06998122-4940-11e6-8f01-43cdf64f2eef.png)
    This feature ensures a certain execution order Notebook with each 
Interpreter.
    ##### Case 3
    
    For concurrent job in the workflow ...
    
    
![job_repl](https://cloud.githubusercontent.com/assets/10525473/16828860/96e601b8-49ce-11e6-87d0-6f7fc30ce751.png)
    
    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
    
    ![cap 2016-07-14 15-11-07-036]
    ### Questions:
    - Does the licenses files need update? no
    - Is there breaking changes for older versions? no
    - Does this needs documentation? yes


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-workflow

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1799.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 #1799
    
----
commit 84daa37f132a968ca381c3d86b6f74e834256e26
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-23T07:31:10Z

    added remote work job status class and get method on interface

----


---
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.
---

Reply via email to