[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor reopened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829 Author: Igor DrozdovDate: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user DrIgor closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user DrIgor closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor reopened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829 Author: Igor DrozdovDate: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor reopened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829 Author: Igor DrozdovDate: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user DrIgor closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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. ---
[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor opened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit b1dd6a33040b17be7cd52a8c482062453a00ed44 Author: Igor DrozdovDate: 2017-01-23T11:20:38Z Search for interpreter-settings in several jars in folder commit b264c9fff7ea2f721b64eab31fae9abf7c9ba107 Author: Igor Drozdov Date: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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. ---