Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/463#issuecomment-162740944
@jongyoul No, it has the opposite effect -- it makes the build process
cumbersome, much longer than it should be, and prone to failure. It also
creates a plethora of bugs for anything that needs to interface against Spark.
These bugs express themselves as errors like the one @tromika found, which are
difficult and time-consuming to trace.
I've spent many, many hours dealing with this issue.
@Leemoonsoo Told me that support for spark out of the directory is coming
out of Zeppelin entirely, and that's already in a pending PR.
Is there any purpose to this other than to support Spark from the
directory? If there is a legitimate purpose, then someone can create a PR that
won't break everything, and makes the dependencies *maintainable*
going-forward. That is certainly not the case here.
If the only purpose is to support Spark from the directory, then this PR
has no purpose at all, since that is no longer a supported feature.
Either way, this PR is going to impose a great deal of time and effort on
others, and it doesn't make sense.
---
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.
---
