All required tests as prescribed by the release guidelines 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.
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:
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.
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:
ACCUMULO-2329, ACCUMULO-2331, and ACCUMULO-2332 have been found already against this RC and have respective branches for each that I've already pushed (not yet merged into 1.5.1-SNAPSHOT until this vote is closed). Also relevant are ACCUMULO-1908 and ACCUMULO-1935 as I have some changes that *should* make them a bit more stable.
I believe I'm going to -1 this candidate. None of the issues are sufficient on their own, but I think the collection of them is sufficient to merit fixing and rolling a better candidate.
I also have filed and have fixes for ACCUMULO-2334, in addition to the previously mentioned tickets.
I would still greatly appreciate any feedback from the larger community. I won't cut a new release at least until after the original 72hrs has passed. I'll leave the 1.5.1-RC1 branch intact for at least the 72hrs as well.
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext