Hi Moon & Girish The note has a runAll method that is being used by the cron scheduler. This method iterates the paragraphs and submits each of them for execution in a single go. This can be made to run sequentially by checking the paragraph status before triggering the next paragraph. We can have a config in paragraph settings in ui say "enable skip on failure" which can be checked to see whether next paragraph should be triggered based on the status of the current paragraph. Also the notebook run can be modified to use this runAll method. Your thoughts pls.
Regards Skanda On 09-Mar-2016 11:38 PM, "moon soo Lee" <m...@apache.org> wrote: > Hi Girish, > > Currently, I think there're no simple way. Please feel free to file an > issue on JIRA. > > Technically, RunNote function iterates runParagraph in front-end side > [1]. To make execution stop on paragraph error, > > a) Need to iterate it on backend side by calling [2], otherwise closing > browser window may stop notebook run. > b) [2] need to be modified to not use scheduler from individual > interpreter but use another FIFO scheduler that run all job sequentially. > c) and maybe it's good to an option to choose, current behavior and this > new behavior in front-end side. > > Thanks, > moon > > [1] > https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-web/src/app/notebook/notebook.controller.js#L172 > [2] > https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/Note.java#L397 > > > On Wed, Mar 9, 2016 at 7:44 AM Girish Reddy <gir...@springml.com> wrote: > >> Hello: >> >> It seems the default behavior in Zeppelin is to continue execution of >> paragraph even if one of the paragraph errors out. Is there a way to >> configure it to stop execution as soon as a paragraph errors out? Or is >> this something that needs to be handled in the paragraph code? >> >> Thanks, >> -Girish >> >> >>
