Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs [master]: REST API JSON response status fix #3224

Closed
wants to merge 1 commit into from

Conversation

@jolks jolks changed the title REST API JSON response status fix Docs: REST API JSON response status fix Nov 13, 2018
@jolks jolks changed the title Docs: REST API JSON response status fix docs: REST API JSON response status fix Nov 13, 2018
@jolks jolks changed the title docs: REST API JSON response status fix docs [master]: REST API JSON response status fix Nov 14, 2018
@Leemoonsoo
Copy link
Member

Thanks @jolks for the contribution.
LGTM and merge to master

@asfgit asfgit closed this in b31f299 Nov 16, 2018
Leemoonsoo pushed a commit to Leemoonsoo/zeppelin that referenced this pull request Nov 18, 2018
### What is this PR for?
Since v0.8.0, REST API JSON response `status` attribute has changed from `CREATED` to `OK`.

Related source code:
* https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/main/java/org/apache/zeppelin/rest/NotebookRestApi.java
* https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/main/java/org/apache/zeppelin/rest/InterpreterRestApi.java

### What type of PR is it?
Documentation

### Questions:
* Shall I add tests to check the returned `status` in:
   * https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/test/java/org/apache/zeppelin/rest/InterpreterRestApiTest.java
   * https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/test/java/org/apache/zeppelin/rest/NotebookRestApiTest.java

Author: John Lau <jolks@outlook.com>

Closes apache#3224 from jolks/doc_rest_api_fix and squashes the following commits:

9037b55 [John Lau] REST API JSON response status fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants