Re: Integrating vendor-specific code and developing plugins

> On May 15, 2017, at 6:57 PM, 大平怜 wrote: > > Thanks for the discussion, all, > >>> * What's included when shipped in tree? >>> >>> Does every idea get merged in? Do we need 30 different Seed providers? Who >>> judges what's valuable enough to add? Who maintains it

Re: Integrating vendor-specific code and developing plugins

Thanks for the discussion, all, >> * What's included when shipped in tree? >> >> Does every idea get merged in? Do we need 30 different Seed providers? Who >> judges what's valuable enough to add? Who maintains it when it needs >> updating? If the maintainer can't be found, is it removed?

rebuilding cassandra.apache.org docs

Looks like the docs haven't been rebuilt in a while. There's a handful of useful merges recently that I'm aware of that would be great to see on there. How do they get rebuilt? Who can trigger it? Jon

Re: Integrating vendor-specific code and developing plugins

Absolutely + Separate repos for separate modules also separate responsibility. IMHO it makes a heterogenuous structure more manageable. Both in a technical and a human or insitutional way. 2017-05-15 13:54 GMT+02:00 Jonathan Haddad : > There's a handful of issues I can think

Re: Integrating vendor-specific code and developing plugins

Hi all, I have suggested some modifications in CASSANDRA-13270 to be able to provide elasticsearch as a plugin, and these changes are available in a fork at https://github.com/strapdata/cassandra Of course, i don’t expect to include this in the cassandra

Re: Integrating vendor-specific code and developing plugins

There's a handful of issues I can think of with shipping everything in-tree. I'll try to brain dump them here. * What's included when shipped in tree? Does every idea get merged in? Do we need 30 different Seed providers? Who judges what's valuable enough to add? Who maintains it when it