Decision making taking more time than I expected and
I think this shouldn't be blocker for 0.7.0.
We can take more time deciding which interpreters can be included or
excluded.
Until then, I am just going to go with our current one: zeppelin-bin-all,
zeppelin-bin-netinst.
Moon's suggestion looks
Hi,
I think we need to have some policy to decide which interpreter goes into
zeppelin-bin-min package. And make applying that policy as a part of
release process.
Because i can not see any consistent rule except for "it seems" or "i
guess". And i have no idea how i can explain if somebody ask 'wh
Thank you for sharing your opinion guys.
I like Eric's approach.
We are planning to provide official docker managed by community.
There is ongoing work [1] around it, I can focus on this after 0.7.0
release.
It seems that majority prefers binary package with top used interpreters
such as spark, m
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
wrote:
> Can I throw out an alternate approach? I feel like the key value of the
> “-all” option is to simplify the l
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
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 wh
Hi,
+1 for releasing netinst package only.
Regarding make binary package only some packages, like spark, markdown,
jdbc, we have discussed having minimal package in [1].
And i still think it's very difficult to decide which interpreter need to
be included which is not. For example i prefer to hav
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. Interpre
+1 for Jeff's idea! I also use the three interpreters mainly :)
2017년 1월 18일 (수) 오후 12:52, Jeff Zhang 님이 작성:
>
> 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
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 于2017年1月18日周三 上午11:33写道：
> Thanks Mina always!
> +1 for releasing only netinst package.
>
Thanks Mina always!
+1 for releasing only netinst package.
On Wed, Jan 18, 2017 at 12:29 PM, Prabhjyot Singh 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 tha
+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" wrote:
> +1
>
> I think
+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"
+1, we should also mention it in release note and in the 0.7 doc
Mina Lee 于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
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
15 matches
Mail list logo
