GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2240
ZEPPELIN-2386. Add parameter for check running current paragraph in
ZeppelinContext
### What is this PR for?
I can reproduce it via the test code in ZeppelinIT.testAngularDisplay.
First run the 4 paragraphs to initiate the state. Then when I click paragraph 0
the first time, paragraph 2 will run correctly. But if I click paragraph 0
again, interpreter would raise the following exception. The cause is that
ZeppelinContext's interpreterContext now point to paragraph 2, because
paragraph 2 is the last paragraph that runs in this interpreter. So I propose
to add parameter to
### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
### Todos
* [ ] - Task
### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg.
[ZEPPELIN-533]
### How should this be tested?
Outline the steps to test the PR here.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2386
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2240.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2240
----
commit 5cf771103fc38008b11910573eabd218f81ebd88
Author: Jeff Zhang <[email protected]>
Date: 2017-04-11T06:21:53Z
ZEPPELIN-2386. Add parameter to check running current paragraph in
ZeppelinContext
----
---
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.
---
