Github user xiufengliu commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@cloverhearts Is this feature available now? I am really looking forward
to. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@rasehorn @zjffdu
Thank you very much!
I understand the function wait.
I will try to organize it again based on your opinion.
Thank you for your kind comments.
---
If your
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@cloverhearts
I think a picture and some pseudocode tells more than thousand words, so I
created one.
Also: I'm only talking about the use case to ensure a certain sequence of
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
As far as I remember another discussion the paragraph IDs will change if
you export/import or copy a notebook (not sure which one applies). If that is
the case the workflow will be broken after
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
Yes, apart from workflow, this feature is essential. (Get paragraph status)
I want to separate getZeppelinJobStatus () into a separate PR, and I want
to improve the workflow by
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@Leemoonsoo
Yes it seems to be good, I will make a new change.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1799
```
z.getZeppelinJobStatus("execute note id", "execute paragraph
id").getJobStatus()
```
How about not repeating `Job`, `Status` and omit `Zeppelin` (while `z.`
represents
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
I'm also a little bit confused what this PR really is about - the pictures
above point to paragraph execution order and control but the discussion also
points to Notebook execution workflows.
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
From my point of view this kind of functionality shall be provided by the
core framework.
I do not have created many notebooks but what I've done always is: create
one paragraph after the
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@zjffdu
Yes you are right.
---
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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1799
Thanks @cloverhearts , after reading #1176. This PR is the first phase of
this feature (implement low level api for workflow), is that correct ?
---
If your project is set up for it, you can
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@zjffdu
I agree with you.
But I am a bit cautious about this part.
In fact, we've re-implemented this functionality in a variety of ways, and
we've actually implemented it in the
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1799
BTW, in the first phase we can provide the high-level framework to allow
user to call it programmatically, And in the second phase, it would be better
to allow user to do it though drag & drop in
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@cloverhearts What I mean is that the code like following would be called
many times by users
```
if (z.getZeppelinJobStatus("execute note id", "execute paragraph
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@cloverhearts This is very interesting. I have a few questions
1. Does the dynamic forms here mean more control flow (like if condition
and for loop)
2. In case 2, If the markdown
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
create new issue on jira
https://issues.apache.org/jira/browse/ZEPPELIN-1886
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
16 matches
Mail list logo
