GitHub user michrawson opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/777

    Allow custom location for interpreter.json and die if not writeable

    ### What is this PR for?
    This will allow for custom location for interpreter.json.
    This will try to create dir if needed.
    This will die if file or file's dir not writeable. 
    
    ### What type of PR is it?
    Bug Fix: Zeppelin can't manipulate notes when deployed to a write only 
directory.
    
    ### How should this be tested?
    1. Test default: when not using a custom file, everything should work as 
usual.
    2. Specify any file via zeppelin-site.xml AND zeppelin-env.sh and that file 
should be used.
    3. If the file exists and is not writeable, zeppelin shouldn't start.
    4. If the file's dir doesn't exit, try to create it.
    5. If the file doesn't exist and the file's dir is not writeable, zeppelin 
shouldn't start.
    
    ### Questions:
    * Does the licenses files need update?
    No
    * Is there breaking changes for older versions?
    No
    * Does this need documentation?
    Added in docs/


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/michrawson/incubator-zeppelin master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-zeppelin/pull/777.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 #777
    
----
commit 5ae1be19f5d09916748b6cc5b29f3e415890fd01
Author: Michael Rawson <mr4...@nyu.edu>
Date:   2016-03-14T17:06:15Z

    Allow custom location for interpreter.json and die if not writeable

----


---
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.
---

Reply via email to