Re: SparkR interpreter question

Thanks! After installing the packages both option worked. What are the differences between the two? -- View this message in context: http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/SparkR-interpreter-question-tp8848p8928.html Sent from the Apache Zeppelin (incubating)

Re: SparkR interpreter question

Try the other interpreter, -Pr to build. If there are dependency issues it will tell you during the build process. > On May 11, 2016, at 10:54 AM, Ethan X wrote: > > Thank you both for your comments. My bad for not following up sooner. The > replies didn't show up in my mailbox for some reason.

Re: SparkR interpreter question

Here are the suggested dependencies to install to get R working with zeppelin: R and the R Packages required to run the R Interpreter and the related R tutorial notebook, including: Knitr, devtools, repr, rCharts, ggplot2, googleVis, mplot, htmltools, base64enc, da

Re: SparkR interpreter question

Thank you both for your comments. My bad for not following up sooner. The replies didn't show up in my mailbox for some reason. I tried building Zeppelin with only the Psparkr option as Jeff suggested, but the interpreter still didn't show up. Here is my building script: mvn clean package -Dskip

Re: SparkR interpreter question

Confirmed, building with both -Pr and -Psparkr will causes errors in zeppelin as this is not an expected build combination. Try building with just one interpreter profile, such as: mvn clean package -DskipTests -Pspark-1.6 -Phadoop-2.6 -Pyarn -Ppyspark -Psparkr Confirmed that R still works on

Re: SparkR interpreter question

Ethan - can you clarify what you mean when you say you couldn't find it? What specifically fails to happen? Are there any log messages? You're attempting to build two separate interpreters, -Pr and -Psparkr both of which want to bind to the same interpreter name, and I don't believe the behavi