[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 https://github.com/apache/zeppelin/pull/1799 I was create new pr. and re-implementation codebased. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 @xiufengliu This feature is currently implemented. I have almost done this change so we can use it as a code implementation of the paragraph. If a fast merge is done, I think I can introduce this feature to you before 2017. Thank you. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user xiufengliu commented on the issue: https://github.com/apache/zeppelin/pull/1176 Dear corneadoug: May I ask if this pull request work is based on the zeppelin 7.0? Are there any problems to use it for now since I saw there are some conflicting files in the above checks? Thanks /Xiufeng --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user xiufengliu commented on the issue: https://github.com/apache/zeppelin/pull/1176 Hi, may i ask if the new PR was open? I am looking forward to this feature --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 @corneadoug Yes, no problem. :) --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user corneadoug commented on the issue: https://github.com/apache/zeppelin/pull/1176 @cloverhearts If I understand, the plan is to open a new PR for this feature? Can it be closed then? --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 This feature is not merged. This feature will be re-implemented. However, because there are people who need it, and I hope to continue to manage the `PR`. I will continue the discussion later in a new way. Thank you. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user xiufengliu commented on the issue: https://github.com/apache/zeppelin/pull/1176 Thanks! It is a fantastic feature. I am really looking forwards to. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 @xiufengliu Thanks for your interest in this feature. This feature can undermine the existing problems Zeppelin used consistently. I would like to re-implement this feature in different ways. If you ever write a Comment about the environment, or purpose you want to use you use, we seem to be a lot of help to improve and implement this feature. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 Thank you for your answer. I would restart operations soon to organize your information. I plan to expand the . If anyone have a different opinion, please write to comment. Thank you. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1176 z.run() currently submit paragraph into each interpreter's scheduler. Let's say there're PARAGRAPH_1, PARAGRAPH_2, PARAGRAPH_3 ``` %md ... %spark ... %sql ... ``` When user execute ``` z.run(P1) z.run(P2) z.run(P3) ``` z.run(P1) submit a job to run P1 to scheduler of Markdown interpreter. z.run(P2) submit a job to run P2 to scheduler of Spark interpreter. z.run(P3) submit a job to run P3 to scheduler of SparkSQL interpreter. And each scheduler from each different interpreter works independently. That's why P1, P2, P3 runs concurrently. (and this is why 'Run all' button doesn't run paragraph sequentially) Then we can add synchronous option, such as ``` val result1 = z.runSynchronously(P1) val result2 = z.runSynchronously(P2) val result3 = z.runSynchronously(P3) ``` Then we can make sure P2 is not submitted before P1 finishes, P3 is not submitted before P2 finishes. My points are, - We can provide API to interpreter runs notebook or paragraph in the other notebook. So user can define workflow in programming language (i.e. scala, python, etc). It naturally gives more flexibility and power user to creates workflow, because programming language provides such things: conditional block, future, threads, and so on. - To provide sequential job execution, we can provide synchronous api such as `z.runSynchronously()` - In case of users, who are not familiar with programming language, want to creates workflow, we can create %workflow interpreter and invent new syntax or GUI on top of the same `z.run()` API internally. This is more modular and less confusing compare to run workflow with dynamic form syntax. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 @corneadoug Your opinion is right. should be added to the . But I was thinking that it must be able to control even in Note. to use convenient and it is true that I am expressing the workflow. Satisfied. However, I'm not sure Whether this is correct. In particular usability and consistency. <% Workflow> @Leemoonsoo 's idea is good. If you have any other idea, please advise me. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
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 is thought that the user wants to manage the workflow Note. I am satisfied with the usability of the workflow according to the . However, there was doubt whether this is also no problem using the . 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 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user corneadoug commented on the issue: https://github.com/apache/zeppelin/pull/1176 I like the idea, but I also don't think that a new dynamic form is a good way to manage it. I think that feature could fit better inside of the JOB page, especially since it is cross-notebook. JOB page is currently only listing the Notebooks and the status of each paragraph, we could see it as a way to manage any workflow. (Full Notebook, or Custom Workflow) I also wonder how can we handle the case of paragraphs that can run in parallel during one of the workflow step. (multiple sql queries for example) There was a lot of demands to have a better 'Run all paragraphs' feature, and maybe we could later have a dropdown on the run button allowing to run multiple profile (to run some workflow related to that notebook, a bit like building different profile in Eclipse) --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user xiufengliu commented on the issue:
https://github.com/apache/zeppelin/pull/1176
`z.run("Paragraph1")
z.run("Paragraph2")
`
will "Paragraph1" and "Paragraph2" run sequencially? If "Paragraph1"
failed, will ""Paragraph2"" still run?
---
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.
---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1176
update
add operator : all paragraph (*)
and ui fixed.
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}
```
---
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.
---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 Thank you for your opinion. I understood as a story about running redundant during 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. Did you find this answer? --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/1176 Cool feature, even I wanted to have something similar. Will test it, and give more feedback, in the mean while, and referring to the gif posted in screenshot segment, can the rest of the paragraph go into pending state. For example in this case can the last paragraph `%md` go into pending state while `%spark` was executing ? --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 jira re link - ZEPPELIN-1165 https://issues.apache.org/jira/browse/ZEPPELIN-1165 --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 update to description. This feature ensures a certain execution order Notebook with each Interpreter. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 @AhyoungRyu It has been completed. However, if the part you want, please tell us at any time. Thank you. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1176 Test description modified. --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1176 Great feature! Can you add documents for this or please explain more detail to review? --- 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. ---
[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1176 @cloverhearts Is this PR WIP? --- 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. ---
