GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/645
ZEPPELIN-612 Introduce 'Configuration' page with WebSocket API / REST API
### What is this PR for?
To introduce 'Configuration' page to Zeppelin GUI. Also introduce REST API
/ WebSocket operation.
### What type of PR is it?
Feature
### Todos
### Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-612
### How should this be tested?
- apply this PR
- build and start Zeppelin
- open UI and confirm Configuration tab is shown
- open Configuration page and confirm every configurations (properties)
except password are shown
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes, I've address it regarding REST API.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/incubator-zeppelin ZEPPELIN-612
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/645.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 #645
----
commit 6acb4e9f59ebb648d62502af82376e208ac6a581
Author: Jungtaek Lim <[email protected]>
Date: 2016-01-16T12:00:59Z
ZEPPELIN-612 Introduce APIs which shows list of configurations via
WebSocket / REST API
commit 49dcae10af774b43c070ed302f1f003e1a649b77
Author: Jungtaek Lim <[email protected]>
Date: 2016-01-16T14:10:02Z
ZEPPELIN-612 Add 'Configuration' page
* which shows key/value pairs of configuration
commit 78bca0036e32e6b8dc04b75357d318614375ed58
Author: Jungtaek Lim <[email protected]>
Date: 2016-01-16T14:27:25Z
ZEPPELIN-612 Add 'Configuration' doc page to navigation
commit 491ff8275629b91443fd2738444d4be25792591e
Author: Jungtaek Lim <[email protected]>
Date: 2016-01-16T14:39:15Z
ZEPPELIN-612 remove unused file
----
---
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.
---
