I like to deploy netinst only. And it's good idea that Apache Zeppelin supports official docker image with all possible interpreters.
On Wed, Jan 18, 2017 at 7:42 PM, Eric Pugh <[email protected]> wrote: > Can I throw out an alternate approach? I feel like the key value of the > “-all” option is to simplify the life of someone who is new to Zeppelin. > If you’re a sophisticated Zeppelin user, then picking and choosing > interpreters is easy, and you you grok why you want to do that…. > > However, for myself, when I want to demo Zeppelin, I go straight to one of > the Docker images, specifically https://github. > com/dylanmei/docker-zeppelin because it bundles in everything. > > Would providing a similar Docker image on the “Get Zeppelin” page that > bundles in all the dependencies and interpreters solve the “how do I try > Zeppelin in 5 minutes” challenge? The “Get Zeppelin” page is rather > daunting page! > > Eric > > > On Jan 18, 2017, at 12:00 AM, Mohit Jaggi <[email protected]> wrote: > > Including ALL interpreters is not feasible, not due to download size as > that is easily increased but because we wouldn't want to couple the release > cycles as pointed out by Jeff. IMHO a few of the most popular ones should > be included. Yes it is just one extra step but if a computer can do it why > make a human suffer? :-) > Re: spark-packages, Spark does include important and mature functionality > in its assembly e.g. Csv parser was merged into core spark when it matured. > I believe Z should do the same. > > Sent from my iPhone > > On Jan 17, 2017, at 8:05 PM, Jeff Zhang <[email protected]> wrote: > > > Another thing I'd like to talk is that should we move most of interpreters > out of zeppelin project to somewhere else just like spark do for > spark-packages, 2 benefits: > > 1. Keep the zeppelin project much smaller > 2. Each interpreter's improvements won't be blocked by the release of > zeppelin. Interpreters can has its own release cycle as long as > zeppelin-interpreter doesn't break the compatibility. > > If it make sense, I can open another thread to discuss it. > > > > > Jun Kim <[email protected]>于2017年1月18日周三 上午11:55写道： > >> +1 for Jeff's idea! I also use the three interpreters mainly :) >> >> 2017년 1월 18일 (수) 오후 12:52, Jeff Zhang <[email protected]>님이 작성: >> >> >> How about also include markdown and jdbc interpreter if this won't cause >> binary distribution much bigger ? I guess spark, markdown, and jdbc >> interpreters are the top 3 interpreters in zeppelin. >> >> >> >> Ahyoung Ryu <[email protected]>于2017年1月18日周三 上午11:33写道： >> >> Thanks Mina always! >> +1 for releasing only netinst package. >> >> On Wed, Jan 18, 2017 at 12:29 PM, Prabhjyot Singh < >> [email protected]> wrote: >> >> +1 >> >> I don't think it's a problem now, but if it keeps increasing then in the >> subsequent releases we can ship Zeppelin with few interpreters, and mark >> others as plugins that can be downloaded later with instructions with how >> to configure. >> >> On Jan 18, 2017 8:54 AM, "Jun Kim" <[email protected]> wrote: >> >> +1 >> >> I think it won't be a problem if we notice it clear. >> Maybe we can do that next to the download button here ( >> http://zeppelin.apache.org/download.html) >> A message may be "NOTE: only spark interpreter included since 0.7.0. If >> you want other interpreters, please see interpreter installation guide" >> >> 2017년 1월 18일 (수) 오후 12:14, Jeff Zhang <[email protected]>님이 작성: >> >> >> +1, we should also mention it in release note and in the 0.7 doc >> >> >> >> Mina Lee <[email protected]>于2017年1月18日周三 上午11:12写道： >> >> Hi all, >> >> Zeppelin is about to start 0.7.0 release process, I would like to discuss >> about binary package distribution. >> >> Every time we distribute new binary package, size of the >> zeppelin-0.x.x-bin-all.tgz package is getting bigger: >> - zeppelin-0.6.0-bin-all.tgz: 506M >> - zeppelin-0.6.1-bin-all.tgz: 517M >> - zeppelin-0.6.2-bin-all.tgz: 547M >> - zeppelin-0.7.0-bin-all.tgz: 720M (Expected) >> >> Mostly it is because the number of interpreters supported by zeppelin >> keeps growing, >> and there is high chance that we support more interpreters in the near >> future. >> So instead of asking apache infra team to increase limit, >> I would like to suggest to have only zeppelin-0.7.0-bin-netinst.tgz, >> which only includes spark interpreter from 0.7.0 release. >> One concern is that users need one more step to install the interpreters >> they use, >> but I believe it can be done easily with single line of command [1]. >> >> FYI, attaching the link of similar discussion [2] we had last June in >> mailing list. >> >> Regards, >> Mina >> >> [1] http://zeppelin.apache.org/docs/0.6.2/manual/ >> interpreterinstallation.html#install-specific-interpreters >> <http://zeppelin.apache.org/docs/0.6.2/manual/interpreterinstallation.html> >> [2] https://lists.apache.org/thread.html/4b54c034cf8d691655156e0cb64724 >> 3180c57a6829d97aa3c085b63c@%3Cusers.zeppelin.apache.org%3E >> >> -- >> Taejun Kim >> >> Data Mining Lab. >> School of Electrical and Computer Engineering >> University of Seoul >> >> >> -- >> Taejun Kim >> >> Data Mining Lab. >> School of Electrical and Computer Engineering >> University of Seoul >> > > > _______________________ > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 > | http://www.opensourceconnections.com | My Free/Busy > <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless > of whether attachments are marked as such. > > -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net
