GitHub user zjffdu opened a pull request:

    https://github.com/apache/zeppelin/pull/1745

    ZEPPELIN-1785. Remove ZEPPELIN_NOTEBOOK_DIR and ZEPPELIN_INTERPRETER_DIR 
from common.sh

    ### What is this PR for?
    We should remove `ZEPPELIN_NOTEBOOK_DIR` and `ZEPPELIN_INTERPRETER_DIR` 
from `common.sh` otherwise the corresponding property defined in 
`zeppelin-site.xml` won't take effect. I also check other properties like 
ZEPPELIN_CONF_DIR and ZEPPELIN_WAR. Although we define them explicitly in 
common.sh, we didn't expose them in document `install.md` and 
`zeppelin-site.xml.template`, so I think these are only for internal use and it 
is OK to keep them in common.sh although their correponding property in 
zeppelin-site.xml won't take effect too. 
    
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1785
    
    ### How should this be tested?
    Tested manually
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    
    …

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

    $ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-1785

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

    https://github.com/apache/zeppelin/pull/1745.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 #1745
    
----
commit 141ec68f98fd215664efb36506e1a38d295f461c
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-12-12T05:31:15Z

    ZEPPELIN-1785. Remove ZEPPELIN_NOTEBOOK_DIR and ZEPPELIN_INTERPRETER_DIR 
from common.sh

----


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