GitHub user benoyantony reopened a pull request:
https://github.com/apache/zeppelin/pull/1623
ZEPPELIN-1625 add support for user specific properties
### What is this PR for?
User should be able to define properties and these properties must be
passed to Interpreter via Interpreter Context.
Add functionality so that Interpreter can substitute the its property value
with the value specified by the user.
### What type of PR is it?
Feature
### Todos
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1625
### How should this be tested?
unit tests provided
Manual testing steps:
Add a property, update the property and then delete it
### Screenshots (if appropriate)
Available in documentation
### Questions:
* Does the licenses files need update? NO
* Is there breaking changes for older versions? NO
* Does this needs documentation? Yes, Documentation is provided.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benoyantony/zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1623.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 #1623
----
commit 0a9e7655d50811988ecd60ab291be44e3927b7c2
Author: Benoy Antony <be...@apache.org>
Date: 2016-11-11T19:06:09Z
add support for user specific properties
commit aeead93d2e1bd882e239ef38cbc91a0380eb6057
Author: Benoy Antony <be...@apache.org>
Date: 2016-11-11T20:50:25Z
Add licenses to new files
commit d07f0bb04f99f281d8f9837f3c102529c582f165
Author: Benoy Antony <be...@apache.org>
Date: 2016-11-12T06:19:14Z
adding license
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
