On Fri, 26 Oct 2012, Joe Buck wrote: > Noah and I talked about this a bit and the idea was not to push our code > upstream, but rather to host a fork locally so that we could decide when > to rev the version(s) we build against rather than just pulling trunk > from Hadoop's repo. We'd still be building the one or two .jar files > that users would have to configure Hadoop to find, but we'd have a full > version of Hadoop in our repo for consistency and what not.
This sounds like the right approach. Which repo to fork? https://github.com/apache/hadoop ? sage > > -Joe Buck > > On Oct 26, 2012, at 3:42 PM, Gregory Farnum wrote: > > > On Fri, Oct 26, 2012 at 3:29 PM, Noah Watkins <[email protected]> wrote: > >> Development of the Hadoop shim layer is best done in the Apache Hadoop > >> Git repository, so we can track up-stream and build for all the > >> different versions that exist. Is keeping a clone in Inktank Github > >> something that is possible / desired? > > > > Are we sure we want to maintain it in a fork of their repo? (I'm not > > saying we don't, just curious.) QFS recently published support for > > Hadoop and apparently they only need two JARs to support the things > > that everybody is running now. Either way, see > > http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201210.mbox/%3ccc946699.1c97b%[email protected]%3E > > and https://issues.apache.org/jira/browse/HADOOP-8885 for the > > discussion surrounding (not) sending that upstream and the > > distribution strategy they ended up with. > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
