cloverhearts 5eeebeb0aa [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 Author: cloverhearts <cloverheartsdev@gmail.com> Closes #1814 from cloverhearts/ZEPPELIN-STATUS-CHANGE-API and squashes the following commits: 0f2f5bd [cloverhearts] change test case in notebooksecurity 1be0968 [cloverhearts] fixed more isCreated to isAllowed cfcb6fd [cloverhearts] change test case in zeppelin rest api test 7bbfcd1 [cloverhearts] change status value in test case http f9fcbc8 [cloverhearts] Revert "refix" ed31788 [cloverhearts] refix 754309e [cloverhearts] Apply to api success status code 200		2017-01-19 22:22:26 -08:00
..
rest-configuration.md	[ZEPPELIN-1219] Add searching feature to Zeppelin docs site	2016-08-10 12:39:22 +09:00
rest-credential.md	[ZEPPELIN-1219] Add searching feature to Zeppelin docs site	2016-08-10 12:39:22 +09:00
rest-helium.md	[ZEPPELIN-1619] Load js package as a plugin visualization	2017-01-14 10:27:17 -08:00
rest-interpreter.md	[ZEPPELIN-1869] changed the API response to generate to 200.	2017-01-19 22:22:26 -08:00
rest-notebook.md	[ZEPPELIN-1869] changed the API response to generate to 200.	2017-01-19 22:22:26 -08:00