Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157040049
And if you are not comfortable working with Zeppelin community, not because
of you're wrong or Zeppelin community is wrong, but maybe just because of the
way we want to go and how we want to get there is little bit different. Keeping
RInterpreter as a 3rd party interpreter is another option.
I think in the future, Zeppelin will have more intuitive way to load and
run 3rd party Interpreters (although it's already possible without rebuild
Zeppelin in a simple way. ie. by deploying binaries under /interpreter and
adding configuration into zeppelin-site.xml). Then using 3rd party interpreter
will be much more easier. Maybe Just few clicks to download and use it.
So keeping as a 3rd party interpreter and take more control of it is
another way you can choose.
I personally think having SparkR as built-in interpreter is really nice to
have for users.
But having rich 3rd party interpreter community is also important for
Zeppelin. (And that's why Zeppelin community need more intuitive way to use 3rd
party interpreter).
So both way, I'm feeling totally fine. Choice is yours.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
