That's right, run paragraph synchronously api is better.
于2020年2月14日周五 下午6:51写道：
> Thanks Jeff, it works fine J
>
>
>
> *From:* Jeff Zhang [mailto:zjf...@gmail.com]
> *Sent:* Friday, February 14, 2020 09:59
> *To:* users
> *Subject:* Re: End of completion for z.runParagraph
>
>
>
> One
於 2020年2月13日 週四 下午6:02寫道：
>
> Hello all,
>
>
>
> I’d like to trigger many paragraphs execution from an angular one. If I
> launch many spark ones, they are executed one after each other, but if I mix
> spark and angular ones, angular ones are triggered even if spark ones are not
> finished
"Management is doing things right; leadership is doing the right things."-
Peter Drucker
Mário Batista
Service Owner
GS GSD CTO Deploy PM NI FF AUT
Mobile:+351 93 997 2637
Upcoming absence:
-Original Message-
From: lee seiching
Sent: Friday, February 14, 2020 12:36 PM
To:
Hello Jeff,
So does this mean that there is no solution?
From: Jeff Zhang [mailto:zjf...@gmail.com]
Sent: Friday, February 14, 2020 09:33
To: users
Subject: Re: End of completion for z.runParagraph
z.run is non-blocking call, it would just trigger the paragraph execution.
The reason
One workaround I can think of is using the rest api to get the paragraph
status.
http://zeppelin.apache.org/docs/0.8.2/usage/rest_api/notebook.html#get-the-status-of-a-single-paragraph
于2020年2月14日周五 下午4:34写道：
> Hello Jeff,
>
>
>
> So does this mean that there is no solution?
>
>
>
> *From:*
Or maybe run a paragraph synchronously:
http://zeppelin.apache.org/docs/0.8.2/usage/rest_api/notebook.html#run-a-paragraph-synchronously
?
From: Jeff Zhang [mailto:zjf...@gmail.com]
Sent: Friday, February 14, 2020 09:59
To: users
Subject: Re: End of completion for z.runParagraph
One
z.run is non-blocking call, it would just trigger the paragraph execution.
The reason why you see spark paragraphs running one after one is because of
spark interpreter use FIFOScheduler
于2020年2月13日周四 下午6:20写道：
> Hello Jeff,
>
>
>
> Thanks for your answer. Here is what I want to do:
>
>
>
>
>
