Ok, after chatting with you off list, I figured out where my confusion was. You built against the default profile (Hadoop 1) and then ran those artifacts on a Hadoop 2.2.0 cluster. I am happy with that testing configuration.
My initial impression was that you built against Hadoop 2, tested against Hadoop 2.2.0, and uploaded Hadoop 1 binaries. I'll vote after I get a chance to run through some more tests. Thanks for putting this together, Josh! On Wed, Feb 5, 2014 at 11:38 AM, Josh Elser <[email protected]> wrote: > Ack - > > No, these jars are not the same, because testing was about a 3-4 week > endeavor. As such, multiple bug fixes were applied to the code base to fix > test cases. So, no: the jars were not the same; however, the changes that > were made across these tests that I run were of little consequence. > > I can provide you the SHA1's from each test I ran if you want > cross-reference each test with the changes that were made. > > > On 2/5/14, 11:35 AM, Josh Elser wrote: > >> No >> >> On 2/5/14, 11:31 AM, Mike Drob wrote: >> >>> Are the jars in the repository the same ones that got loaded onto your >>> clusters for testing? >>> >>> >>> On Wed, Feb 5, 2014 at 11:21 AM, Josh Elser <[email protected]> >>> wrote: >>> >>> No, the jars in the repo were built against the default profile. I >>>> omitted >>>> saying that I used the `assemble/build.sh --create-release-candidate` as >>>> the baseline. The profiles it activates are the ones I used. >>>> >>>> Although all of this shouldn't even matter. We haven't needed to build >>>> against specific profiles for quite some time now in >=1.5. >>>> >>>> >>>> On 2/5/14, 11:16 AM, Mike Drob wrote: >>>> >>>> Are the jars in the staging repository built against the Hadoop 2 >>>>> profile >>>>> as well, then? I was under the impression that Hadoop 1 was still the >>>>> default profile. >>>>> >>>>> >>>>> On Wed, Feb 5, 2014 at 10:11 AM, Josh Elser <[email protected]> >>>>> wrote: >>>>> >>>>> Hadoop: 2.2.0 >>>>> >>>>>> Zookeeper: 3.4.5. >>>>>> On Feb 5, 2014 9:56 AM, "Mike Drob" <[email protected]> wrote: >>>>>> >>>>>> Which version of hadoop/zookeeper did you test against for the >>>>>> cluster >>>>>> >>>>>>> tests? >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 4, 2014 at 11:29 PM, Josh Elser <[email protected]> >>>>>>> >>>>>>> wrote: >>>>>> >>>>>> >>>>>>> All, >>>>>>> >>>>>>>> >>>>>>>> Please consider the following candidate as Apache Accumulo 1.5.1 >>>>>>>> >>>>>>>> Git artifacts: The staging repository was built from the branch >>>>>>>> "1.5.1-rc1" (09e420bb). No accompanying git tag was created yet >>>>>>>> (as it >>>>>>>> would be the same exact thing as providing the above SHA1). >>>>>>>> >>>>>>>> Maven Staged Repo: >>>>>>>> https://repository.apache.org/content/repositories/ >>>>>>>> orgapacheaccumulo-1000/ >>>>>>>> >>>>>>>> Source tarball: http://repository.apache.org/content/repositories/ >>>>>>>> orgapacheaccumulo-1000/org/apache/accumulo/accumulo/1.5. >>>>>>>> 1/accumulo-1.5.1-src.tar.gz >>>>>>>> >>>>>>>> Changes since 1.5.0: https://git-wip-us.apache.org/ >>>>>>>> repos/asf?p=accumulo.git;a=commitdiff;h= >>>>>>>> d277321d176b71753d391f896f09dc >>>>>>>> >>>>>>>> 9785173cb0 >>>>>>>> >>>>>>>> Keys: http://www.apache.org/dist/accumulo/KEYS >>>>>>>> >>>>>>>> Testing: >>>>>>>> >>>>>>>> All required tests as prescribed by the release guidelines[1] were >>>>>>>> successfully completed. Randomwalk and continuous-ingest tests were >>>>>>>> completed on a 6-node installation. JUnit and functional tests >>>>>>>> >>>>>>>> successfully >>>>>>> >>>>>>> completed on a single Linux box. >>>>>>>> >>>>>>>> This vote will be open for the next 72 hours. >>>>>>>> >>>>>>>> Upon successful completion of this vote, a 1.5.1 gpg-signed Git tag >>>>>>>> >>>>>>>> will >>>>>>> >>>>>> >>>>>> be created from 09e420bb and the above staging repository will be >>>>>>> >>>>>>>> >>>>>>>> promoted. >>>>>>> >>>>>>> >>>>>>>> - Josh >>>>>>>> >>>>>>>> [1] http://accumulo.apache.org/governance/releasing.html >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>
