You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by cloverhearts <gi...@git.apache.org> on 2017/01/21 15:16:23 UTC
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1930
[ZEPPELIN-1886] implementation z.getZeppelinJobStatus
### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.
related
https://github.com/apache/zeppelin/pull/1799
### What type of PR is it?
Feature
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1886
### How should this be tested?
1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
z.getZeppelinJobStatus("notid", "paragraphid").getStatus()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-GET-PARAGRAPH-STATUS
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1930.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 #1930
----
commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cl...@gmail.com>
Date: 2016-12-30T22:29:38Z
extends z.status on RemoteWorks
commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-01T05:53:09Z
implement check status logic in workflow
commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T15:10:10Z
add status getter
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1930
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1930
[ZEPPELIN-1886] implementation z.getZeppelinJobStatus
### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.
related
https://github.com/apache/zeppelin/pull/1799
### What type of PR is it?
Feature
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1886
### How should this be tested?
1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
%spark
z.getJobStatus("noteID", "paragraphId").name()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-GET-PARAGRAPH-STATUS
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1930.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 #1930
----
commit 43c9ea5051745a013fd78d5a9497e960d42c6570
Author: cloverhearts <cl...@gmail.com>
Date: 2016-12-30T22:29:38Z
extends z.status on RemoteWorks
commit f0e9825e0e5867b750a8b386c0b82233b3915302
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-01T05:53:09Z
implement check status logic in workflow
commit 44fd762e1e9646deb0fdccfec7e3cabaa2042bfb
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T15:10:10Z
add status getter
commit 7eac7572dcaf81f9b14a255f531fb7df7d465d7e
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:08:42Z
change method name
commit 01614e6be21f7d08038db55b38a6da58744df505
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:55:01Z
added test case
commit cdbdb4ce51453239323e228847f7b6d87cbc2bb6
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T21:43:09Z
remove \u201c
commit b9948df748281579c1998434915b0a9e29dd274d
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-23T22:03:14Z
change test case for println
commit 7ecde8aeca227ff43c7ac2c5bb139dfedbeee4b6
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-23T22:57:53Z
remove println in testcase
commit a6b1719594c481c9236eea639b419526ab7918db
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-24T02:40:24Z
remove "
commit 0482333c3394b878dec5cdb9f60322c6d19a2de5
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-24T07:13:05Z
remove system.out
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1930: [ZEPPELIN-1886] implementation z.getZeppelinJobStatus
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1930
Could you rebase/merge master and see if CI passes?
This branch has a lot of CI build failure which is fixed by https://github.com/apache/zeppelin/pull/1939
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1930
[ZEPPELIN-1886] implementation z.getZeppelinJobStatus
### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.
related
https://github.com/apache/zeppelin/pull/1799
### What type of PR is it?
Feature
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1886
### How should this be tested?
1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
%spark
z.getJobStatus("noteID", "paragraphId").name()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-GET-PARAGRAPH-STATUS
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1930.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 #1930
----
commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cl...@gmail.com>
Date: 2016-12-30T22:29:38Z
extends z.status on RemoteWorks
commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-01T05:53:09Z
implement check status logic in workflow
commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T15:10:10Z
add status getter
commit f2c7df4f99f8db1b2f4b0268f90079226f7c38c4
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:08:42Z
change method name
commit 995b79c57abe8c650be7a534ce3fe8601fd13c56
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:55:01Z
added test case
commit d6e0879ca2a22580aca0b5bfa9667ab30e1f30ca
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T21:43:09Z
remove \u201c
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1930
[ZEPPELIN-1886] implementation z.getZeppelinJobStatus
### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.
related
https://github.com/apache/zeppelin/pull/1799
### What type of PR is it?
Feature
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1886
### How should this be tested?
1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
%spark
z.getJobStatus("noteID", "paragraphId").name()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-GET-PARAGRAPH-STATUS
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1930.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 #1930
----
commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cl...@gmail.com>
Date: 2016-12-30T22:29:38Z
extends z.status on RemoteWorks
commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-01T05:53:09Z
implement check status logic in workflow
commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T15:10:10Z
add status getter
commit f2c7df4f99f8db1b2f4b0268f90079226f7c38c4
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:08:42Z
change method name
commit 995b79c57abe8c650be7a534ce3fe8601fd13c56
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T20:55:01Z
added test case
commit d6e0879ca2a22580aca0b5bfa9667ab30e1f30ca
Author: cloverhearts <cl...@gmail.com>
Date: 2017-01-21T21:43:09Z
remove \u201c
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1930
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1930
---
[GitHub] zeppelin pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1930
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---