Another qualifier is that Bigtop only incorporates released versions of the components - so until Hadoop releases 0.23, we can't incorporate it. 0.20.x->0.23 is also going to particularly hairy due to the major build changes - we'll have to modify how we're building Hadoop in such a way that it won't actually be possible to just drop 0.20.x back in in place of 0.23. We're going to have this same thing show up with Flume 0.94, which also requires Thrift installed on the build boxes, hence me punting that til 0.3.0, which should feature packages of Avro/Thrift/Forrest as well (i.e., the build tools).
A. On Tue, Sep 6, 2011 at 10:15 AM, Roman Shaposhnik <[email protected]> wrote: > On Tue, Sep 6, 2011 at 8:15 AM, Steve Loughran <[email protected]> wrote: > > I'm just tracking this on email, so forgive me if I seem clueless > > > > what versions of the artifacts are being targeted? > > The complete bill of materials for Bigtop is always recorded in: bigtop.mk > https://svn.apache.org/repos/asf/incubator/bigtop/trunk/bigtop.mk > > > Is it the 0.20.20x+ branch of Hadoop w/ things on top, or is it 0.23+ > stuff? > > For the Bigtop 0.1.0 release it was 0.20.2. We are currently figuring out > what > versions of components should we track in Bigtop 0.2.0. If you have any > feedback > for us, please don't hesitate to record it on this JIRA: > https://issues.apache.org/jira/browse/BIGTOP-28 > > Finally, we NEVER ever patch Apache releases: > > https://cwiki.apache.org/confluence/display/BIGTOP/Frequently+Asked+Questions+%28FAQ%29 > > Speaking of which -- I remember this policy preventing us from picking > up 0.20.203, since sadly enough the build there (native part of it) is > broken. > > > Is the goal to target and test both? > > We do this release-by release. > > Thanks, > Roman. >
