I am hearing feedback that Zeppelin is suffering from dependency creep. The problem is that all of the dependencies for all of the interpreters get brought in, no matter which interpreters you actually want.
Leads to problems. Having a clean chinese wall between the core and the optional parts helps this a lot. On Sun, May 17, 2015 at 3:33 PM, Roman Shaposhnik <[email protected]> wrote: > On Thu, May 14, 2015 at 8:44 PM, Alexander Bezzubov <[email protected]> > wrote: > > Roman, James, Jim, Jongyoul, > > > > thank you guys for a feedback. > > > > James's point on community growing though the interpreter > > contributors\maintainers sounds great indeed and difficulties supporting > > external "plugins" with all the versions could overweight the benefits of > > such separation. And especially valuable is experience with Cloundstack > > that Jim brought in. > > > > I really like the idea of mixed model like the one that Jim has > described: > > more mature interpreters should indeed belong to the root, as it is > already > > now, so we just need to find a technical mean of separating early-stages > > ones (until the community steps up to say they are important\mature > enough, > > by maintaining them). > > AFAIK one can also see the same pattern in Apache Spark project. > > > > Any thought on how such "zeppelin-extras" might work? > > Every project I've been part of has always ended up having contrib/ folder > for stuff that had that exact 'incubation -- not for real use' flavor to > it. > > Thanks, > Roman. >
