[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-08-05 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 I have not got any replies on this. Let me close the issue. --- 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 no

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-13 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 @elbamos Thanks for your information. I found that moving "zeppelin-zrinterpreter-0.6.0-SNAPSHOT.jar" to under "interpreter/r" will resolve the issue and enable the registration process for Knitr

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-05 Thread elbamos
Github user elbamos commented on the issue: https://github.com/apache/zeppelin/pull/1077 I'm sorry I have not had a chance to finish addressing this. One issue is that a PR to interpreter.sh removed the rinterpreter jar from the classpath. It needs to be put back in. That will cause k

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-05 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 I think I found the root cause of the problem. The key issue is that currently the build configuration packages "zeppelin-zrinterpreter-0.6.0-SNAPSHOT.jar" under "interpreter/spark" instead of u

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-05 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 @jongyoul Thanks. However, I tried that before and still observed the same behaviour. It seems to be related to something else: i.e., the fact interpreter-setting.json for r interpreter is not re

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-04 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1077 @rerngvit How about stopping Zeppelin, removing conf/interpreter.json, starting Zeppelin and testing it again? --- If your project is set up for it, you can reply to this email and have your rep

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-07-04 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 @jongyoul I have tried to rebuild with -Pr after rebase to master. I did not get the error "org.apache.thrift.TApplicationException: Internal error processing createInterpreter" anymore. Instead,

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-30 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1077 @rerngvit Could you please try to build with `-Pr` after rebase it from current master? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-29 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 @jongyoul I already installed R on my machine. I showed an excerpt of R command from my shell terminal below. As I mentioned above, trying to build with -Psparkr is working fine, which indicates

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-27 Thread elbamos
Github user elbamos commented on the issue: https://github.com/apache/zeppelin/pull/1077 @rerngvit Thanks for looking at this! There were conflicts introduced with the addition of the livy interpreter (or around that time) because sparkr was hard-coded into some of the conf

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-27 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1077 @rerngvit I'm not good at R, if you, however, built with `-Pr` and got an error while creating interpreter, AFAIK, you should have a R installed by default. Could you please check this first? -

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-24 Thread rerngvit
Github user rerngvit commented on the issue: https://github.com/apache/zeppelin/pull/1077 @jongyoul regarding the description text, according to the [build documentation](https://github.com/apache/zeppelin#build), both options should enable R support. Please let me know, if I miss som

[GitHub] zeppelin issue #1077: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

2016-06-24 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1077 @rerngvit In a description, I think `-Psparkr` is not related to this module. we should use `-Pr`, right? --- If your project is set up for it, you can reply to this email and have your reply ap