Github user namanmishra91 commented on the issue:
https://github.com/apache/zeppelin/pull/2619
@zjffdu Yeah, I can change the implementation to make
`persistAndExecuteSingleParagraph` paragraph blocking. Then we won't need UI
side changes for separate event handling etc. However, we will still need other
UI changes for paragraph state management because the execution workflow is
changing. Just to make sure that we are on the same page, let me take a moment
to explain why those will be needed:
Unless we want to change the zeppelin architecture of separate interpreter
queues, we need to hold paragraphs to prevent them from being executed.
Currently all paragraphs get submitted immediately and their status changes to
PENDING. With the above approach, only one paragraph will be in any
interpreter's queue at any given point of time; hence the status of _yet-to-be
executed_ paragraphs will not get updated and the communication to the user
that those paragraphs will run eventually will be lost. This will be a major
change in the UX. We need to discuss and think about what should be the best
way to handle this but as a preliminary implementation, we need to prevent
explicit runs of the paragraphs that are not running yet. This will require
maintaining state about whether a _run all_ is in progress and passing this to
front-end.
Let me know your thoughts on the above.
---
