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
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
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?
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 you
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 fea
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 a
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 discu
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 proj
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 diff
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1176
@xiufengliu No it wasn't merged.
In merged PR you can see a message saying: "asfgit closed this in
CommitHash Xdays ago"
This is an interesting feature and there was some discussions on
Github user xiufengliu commented on the issue:
https://github.com/apache/zeppelin/pull/1176
Hi, may I ask if this feature has been merged to the master?
---
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
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.
Than
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
...
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 expres
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 workf
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-notebo
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1176
Thanks @cloverhearts for the contribution and the descriptions.
And sorry for giving some negative feedbacks here.
**Workflow definition**
I'm not sure about workflow definition
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1176
Screenshot 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 project does not have this feature
enabled and wishes
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1176
update
add operator : all paragraph (*)
and ui fixed.
