If possible, we need to integrate the install script in zeppelin UI. As I would expect many users would ask why some interpreter is missing and how to install them.
moon soo Lee <m...@apache.org>于2017年6月5日周一 上午2:06写道： > Following is last discussion related to release package size. > > > https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E > > at this time, we have discussed about having bin-all (every interpreters), > bin-min (selected interpreters), bin-netinst (no interpreters) package but > didn't conclude the criteria and how we make a decision. > > Jongyoul, do you have any idea about criteria? > > Thanks, > moon > > On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung <felixcheun...@hotmail.com> > wrote: > >> Sure - I think it will be important to discuss what criteria to use to >> decide what is included vs what will be released separately. >> >> _____________________________ >> From: Jongyoul Lee <jongy...@gmail.com> >> > Sent: Sunday, June 4, 2017 9:47 AM >> Subject: Re: [DISCUSS] Reducing default interpreters while building and >> releasing Zeppelin >> To: dev <dev@zeppelin.apache.org> >> > Cc: <us...@zeppelin.apache.org> >> > >> >> >> It means we release with some interpreters and deploy all interpreters >> into >> maven separately. We already had a install-interpreter script inside it. >> If >> someone wants to install specific interpreter not included in default >> release package, they can use that script to install specific one. >> >> On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung <felixcheun...@hotmail.com> >> wrote: >> >> > Are we proposing some interpreters to be built and released separately? >> > >> > Is this going to be separate packaging? Or separate release pipeline? >> > >> > >> > _____________________________ >> > From: Jongyoul Lee <jongy...@gmail.com<mailto:jongy...@gmail.com >> <jongy...@gmail.com>>> >> > Sent: Friday, June 2, 2017 11:04 PM >> > Subject: [DISCUSS] Reducing default interpreters while building and >> > releasing Zeppelin >> > > To: dev <dev@zeppelin.apache.org<mailto:dev@zeppelin.apache.org >> <dev@zeppelin.apache.org>>>, < >> > >> > us...@zeppelin.apache.org<mailto:us...@zeppelin.apache.org >> <us...@zeppelin.apache.org>>> >> > >> > >> > Hi dev and users, >> > >> > > Recently, zeppelin.apache.org<http://zeppelin.apache.org> is being >> > >> > changed for increasing user experiences and convenience. I like this >> kind >> > of changes. I, however, saw some arguments that which interpreters we >> will >> > locate in the first page. I'd like to expand its argument to the >> package we >> > release. >> > >> > Current zeppelin packages exceed 700MB with default option because >> > Zeppelin tried to include all interpreters by default. It was good at >> the >> > early age but, nowadays, Zeppelin community suffer from the size because >> > ASF infra allows the package size under 500MB. So I'd like to reduce the >> > package size by reducing default packages. >> > >> > In case of rebuilding homepage, community proposed some criteria >> including >> > mailing list and # of question in stackoverflow. I think we can adapt >> same >> > criteria into release version of Zeppelin. >> > >> > To handle this kind of issue, I think consensus of community is the most >> > important factor. If someone wants to have an idea to deal with it, >> please >> > feel free to talk about it. >> > >> > Thanks, >> > Jongyoul Lee >> > >> > -- >> > 이종열, Jongyoul Lee, 李宗烈 >> > http://madeng.net >> > >> > >> > >> >> >> -- >> 이종열, Jongyoul Lee, 李宗烈 >> http://madeng.net >> >> >>
