GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1814
[ZEPPELIN-1869] changed the API response to generate to 200.
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.apache.org/contribution/contributions.html
### What type of PR is it?
Documentation | change
### Todos
- [x] replace to doc
- [x] change response 201 -> 200
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1869
### 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-STATUS-CHANGE-API
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1814.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 #1814
----
commit 754309ed4c68e408e48a95d53a460d80fc2935f9
Author: cloverhearts <[email protected]>
Date: 2016-12-29T06:42:07Z
Apply to api success status code 200
commit ed317886f250c246734bb9a947d0bcdfaa352f9b
Author: cloverhearts <[email protected]>
Date: 2016-12-29T07:55:08Z
refix
commit f9fcbc8fbd5a4d6686c0ef4f033694365372deaa
Author: cloverhearts <[email protected]>
Date: 2016-12-29T07:58:58Z
Revert "refix"
This reverts commit ed317886f250c246734bb9a947d0bcdfaa352f9b.
commit 7bbfcd1c24af196c596178a57e2dde33d279956e
Author: cloverhearts <[email protected]>
Date: 2017-01-07T09:01:30Z
change status value in test case http
commit cfcb6fdbe84c92a41e987ad0f026c9b47c517c47
Author: cloverhearts <[email protected]>
Date: 2017-01-07T09:30:12Z
change test case in zeppelin rest api test
commit 1be096822d15ee84786597dc83f5523375abc284
Author: cloverhearts <[email protected]>
Date: 2017-01-07T09:59:50Z
fixed more isCreated to isAllowed
commit 0f2f5bd74630dcc9702d0ecb30b86e483cb4f965
Author: cloverhearts <[email protected]>
Date: 2017-01-07T10:45:59Z
change test case in notebooksecurity
----
---
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.
---
