GitHub user rerngvit opened a pull request:

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

    [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

    ### What is this PR for?
    This PR applies the new interpreter registration mechanism to KnitR and 
RRepl.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    - Move interpreter registration properties from static block to 
interpreter-setting.json
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-921
    
    ### How should this be tested?
    1. apply patch
    2. rm -r interpreter/r
    3. rm conf/interpreter.json
    4. mvn clean package -DskipTests -Pspark-1.6 -Psparkr
    5. bin/zeppelin-daemon.sh start
    6. run some paragraph with simple R queries
    
    ### 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/rerngvit/incubator-zeppelin ZEPPELIN-921

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

    https://github.com/apache/zeppelin/pull/1077.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 #1077
    
----
commit 460ec8dfc548ab71f94ddae83991bfe191602a2f
Author: rerngvit <rerng...@kth.se>
Date:   2016-06-10T06:45:01Z

    [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl
    
    This PR applies the new interpreter registration mechanism to KnitR and 
RRepl.
    
    Improvement
    
    - Move interpreter registration properties from static block to 
interpreter-setting.json
    
    https://issues.apache.org/jira/browse/ZEPPELIN-921
    
    1. apply patch
    2. rm -r interpreter/r
    3. rm conf/interpreter.json
    4. mvn clean package -DskipTests -Pspark-1.6 -Psparkr
    5. bin/zeppelin-daemon.sh start
    6. run some paragraph with simple R queries
    
    Questions:
    
    Does the licenses files need update? No
    Is there breaking changes for older versions? No
    Does this needs documentation? No

----


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