GitHub user zjffdu opened a pull request:

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

    ZEPPELIN-1175. AM log is not available for yarn-client mode

    ### What is this PR for?
    For now, we share the same class path for zeppelin server and remote 
interpreter process. The cause the issue that AM log is not available for 
yarn-client mode because the yarn app also use the 
`ZEPPELIN_HOME/conf/log4j.properties` which is only for zeppelin server. So 
this PR just distinguish the CLASSPATH of zeppelin server and remote 
interpreter process. I use `ZEPPELIN_INTP_CLASSPATH` to represent the classpath 
of remote interpreter process and won't include 
`ZEPPELIN_HOME/conf/log4j.properties` in `ZEPPELIN_INTP_CLASSPATH`. 
    
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1175
    
    ### 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? Yes, if user put custom 
config file (hive-site.xml) under ZEPPELIN_HOME/conf, it won't take effect 
after this PR 
    * Does this needs documentation? Yes
    


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

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

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

    https://github.com/apache/zeppelin/pull/1228.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 #1228
    
----
commit 0973477dcfc84a5121a1e83f6a3f835bfab6e7ea
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-07-26T02:41:50Z

    ZEPPELIN-1175. AM log is not available for yarn-client mode

----


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