On Sun, Aug 9, 2015 at 8:18 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > I had some long talks with Amol on exactly this point when he was getting > started with this proposal. > > At the current time, it appears that the developer communities for these > two systems are indistinguishable. Moreover, neither project is actually > much use without the other. Malhar requires Apex to run and Apex provides > low-level capabilities that are not particularly useful without Malhar. > These two are even more strongly linked than, say Lucene and Solr. Or HDFS > and Yarn. > > The primary difference between these is that Malhar is expected to be > released much more frequently than Apex as new functions are added. Also, > as a platform, there is much more burden on Apex to be stable, thus > decreasing the desirable release frequency. Over time, it is likely that > newcomers are more likely to find it easy to contribute on the Malhar side > initially, but the existing community is fine with keeping the committer > pool uniform.
Ok, that makes sense, but it also leads to the next question. With such tight integration why ask for different JIRAs for the two projects and two different repos? Keeping with your HDFS/YARN analogy, say what you will, but part of the reason Hadoop was able to innovate so quickly was that those were part of the same project. Thanks, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
