Github user sourav-mazumder commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-188283043
As such that approach makes sense to me.
But wondering how will this work for the Zeppelin binary ? Will Zeppelin
binary not have the R support by default because of this ? So whoever wants
to create his own build ?
So instead of that approach I would suggest if this check/constraint can be
moved at run time level instead of compile time. So whoever tries to run
the interpreter gets the error and he/she then goes and install R. I
believe both SparkR and RStudio work in similar fashion.
Regards,
Sourav
On Wed, Feb 24, 2016 at 5:21 AM, Alexander <notificati...@github.com> wrote:
> Guys, please correct me if I'm wrong but current R interpreter
> implementation, in order to be compiled, requires R installed on user's
> machine AND it is included in the default build (at least right now) -
that
> would result in build failing for every user of Zeppelin out there after
> pulling the change.
>
> I think what we may do, without breaking Zeppelin build for all the users,
> is simply exclude R interpreter build from default build cycle of mvn
> package and put it under profile, i.e -P r as we do with scalding,
> pyspark and other interpreters \w external dependencies . This way those
> who do not need R support will not be affected, at the same time those who
> do - will be able to get it.
>
> What do you guy think? Then I could update CI to use this profile as well.
>
> â
> Reply to this email directly or view it on GitHub
>
<https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-188252250>
> .
>
---
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.
---
