Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/980
Thanks for elaborate on idea about 2 lines approach.
I think there're always pros and cons.
If we go to 2 lines approach, code will be cleaner, simpler and more easier
to read.
But this means Zeppelin generally enables create binary per interpreter
dependency because we'll have the same policy for all interpreters. In the
end, i'm afraid we end up with making bunch of binary packages like
- zeppelin with spark 1.x on scala 2.10
- zeppelin with spark 1.x on scala 2.11
- zeppelin with spark 2.0 on scala 2.10
- zeppelin with spark 2.0 on scala 2.11
- zeppelin with spark 2.1 on scala 2.10
- zeppelin with spark 2.1 on scala 2.10
- zeppelin with python3.x
- zeppelin with python2.x
- zeppelin with hive1
- zeppelin with hive2
- .....
In the perspective of user, it can not be an improvement. A single Zeppelin
binary used to work with everything, but now user have to understand difference
between of packages and able to select them before uses.
I think code complexity will not endlessly increase if we cut the spark
support for last x releases.
---
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.
---
