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.
From my point of view the control over paragraph execution within a
notebook is something different than defining a workflow for notebook execution
and mixing different features leads to poor design.
Often paragraphs within notebooks depend on others and therefore they need
to be executed in a certain order. I feel like this kind of paragraph execution
control shall be handeled by the core framework based on settings for each
paragraph within the notebook.
Additionally: In some places within the discussion the implementation of
that feature on interpreter level was mentioned. It is not clear to me why the
notebook workflow definition feature shall be reimplemented in different
interpreters in different ways. Instead the internals of a notebook are of no
interest when it is executed within a workflow - all that matters is success or
failure and a definition at the workflow level what shall happen in case of a
failure. So from my point of view the notebook workflow feature should also be
implemented in the core code independently from the different interpreters
available.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
