svn commit: r891140 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Fri Dec 20 05:16:56 2013
New Revision: 891140
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 20 05:16:56 2013
@@ -1 +1 @@
-1549867
+1552493
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Fri Dec 20 05:16:56 2013
@@ -187,6 +187,7 @@ tr:nth-child(2n+1) {
Sean Hickey
stevelSteve Loughranhttp://hortonworks.com/>Hortonworks(http://www.timeanddate.com/library/abbreviations/timezones/eu/gmt.html>0
/ http://www.timeanddate.com/library/abbreviations/timezones/eu/bst.html>+1)
supunSupun Kamburugamuva
+ tedyuTed Yuhttp://hortonworks.com/>HortonworksPT (http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>-8
/ http://www.timeanddate.com/library/abbreviations/timezones/na/pdt.html>-7)
Tim Halloran
Tim Reardon
Travis Pinney
svn commit: r892991 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Mon Jan 6 13:56:43 2014
New Revision: 892991
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 6 13:56:43 2014
@@ -1 +1 @@
-1552493
+1555768
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Mon Jan 6 13:56:43 2014
@@ -120,6 +120,7 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
acordovaAaron Cordovahttp://www.koverse.com";>Koverse
afuchsAdam Fuchshttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ bhavankiBill Havankihttp://www.cloudera.com/";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
bimarguliesBenson Margulieshttp://www.basistech.com";>Basis Technology Corp.
ET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
billieBillie Rinaldihttp://hortonworks.com/>HortonworksET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
@@ -144,7 +145,6 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
Aaron Glahehttp://www.data-tactics.com/>Data TaticsET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Alex Moundalexishttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
- Bill Havankihttp://www.cloudera.com/";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Chris Bennight
Chris McCubbinhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Christian Rohlinghttp://endgame.com/>EndgameET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r892994 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Mon Jan 6 14:12:15 2014
New Revision: 892994
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 6 14:12:15 2014
@@ -1 +1 @@
-1555768
+1555791
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Mon Jan 6 14:12:15 2014
@@ -120,9 +120,9 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
acordovaAaron Cordovahttp://www.koverse.com";>Koverse
afuchsAdam Fuchshttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
- bhavankiBill Havankihttp://www.cloudera.com/";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
bimarguliesBenson Margulieshttp://www.basistech.com";>Basis Technology Corp.
ET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ bhavankiBill Havankihttp://www.cloudera.com/";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
billieBillie Rinaldihttp://hortonworks.com/>HortonworksET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
brianlossBrian Losshttp://www.praxiseng.com/>Praxis EngineeringET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
cawaringChris Waring
svn commit: r893014 - in /websites/staging/accumulo/trunk/content: ./ papers.html
Author: buildbot Date: Mon Jan 6 16:42:12 2014 New Revision: 893014 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/papers.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Mon Jan 6 16:42:12 2014 @@ -1 +1 @@ -1555791 +1555905 Modified: websites/staging/accumulo/trunk/content/papers.html == --- websites/staging/accumulo/trunk/content/papers.html (original) +++ websites/staging/accumulo/trunk/content/papers.html Mon Jan 6 16:42:12 2014 @@ -93,6 +93,7 @@ Applications http://trendulo.com/";>Trendulo: Twitter trend analysis using Apache Accumulo (https://github.com/jaredwinick/Trendulo";>github code) +https://github.com/search?q=accumulo&type=Repositories";>Search Github for Accumulo Papers and Slides @@ -121,10 +122,6 @@ http://people.apache.org/~kturner/accumulo14_15.pdf";>Accumulo DC Meetup 16 Feb 2012: 1.4 & 1.5 Features http://people.apache.org/~afuchs/slides/morgan_state_talk.pdf";>Accumulo -- Extensions to Google's Bigtable Design. Baltimore ACM Lecture hosted by Morgan State University, March 29, 2012 -Github - -https://github.com/search?q=accumulo&type=Repositories";>Search for Accumulo - Blog Posts and Examples https://github.com/joshelser/node-accumulo";>Node.js, RabbitMQ, and Accumulo @@ -143,6 +140,11 @@ https://gist.github.com/1535657";>Accumulo on Ubuntu VirtualBox http://www.accumulodata.com/ec2.html";>Accumulo on EC2 +Books + +http://www.packtpub.com/apache-accumulo-for-developers/book";>Apache Accumulo for Developers (Packt Publishing) +http://shop.oreilly.com/product/0636920032304.do";>Accumulo: Application Development, Table Design, and Best Practices (O'Reilly Media) + Meetup Groups http://www.meetup.com/Accumulo-Users-DC/";>Accumulo Users Group - DC VA MD @@ -154,6 +156,7 @@ http://research.google.com/archive/bigtable.html";>BigTable http://research.google.com/archive/gfs.html";>GFS http://research.google.com/archive/chubby.html";>Chubby +http://research.google.com/pubs/pub36356.html";>Dapper http://en.wikipedia.org/wiki/Bloom_filter";>Bloom Filter
svn commit: r893077 - in /websites/staging/accumulo/trunk/content: ./ 1.5/examples/dirlist.html
Author: buildbot Date: Mon Jan 6 23:38:12 2014 New Revision: 893077 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/1.5/examples/dirlist.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Mon Jan 6 23:38:12 2014 @@ -1 +1 @@ -1555905 +1556070 Modified: websites/staging/accumulo/trunk/content/1.5/examples/dirlist.html == --- websites/staging/accumulo/trunk/content/1.5/examples/dirlist.html (original) +++ websites/staging/accumulo/trunk/content/1.5/examples/dirlist.html Mon Jan 6 23:38:12 2014 @@ -132,14 +132,14 @@ $ ./$ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.QueryUtil -i instance -z zookeepers -u username -p password -t indexTable --auths exampleVis --path filename --search $ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.QueryUtil -i instance -z zookeepers -u username -p password -t indexTable --auths exampleVis --path 'filename*' --search $ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.QueryUtil -i instance -z zookeepers -u username -p password -t indexTable --auths exampleVis --path '*jar' --search -$ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.QueryUtil -i instance -z zookeepers -u username -p password -t indexTable --auths exampleVis iipath 'filename*jar' --search +$ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.QueryUtil -i instance -z zookeepers -u username -p password -t indexTable --auths exampleVis --path 'filename*jar' --search To count the number of direct children (directories and files) and descendants (children and children's descendants, directories and files), run the FileCount over the dirTable table. The results are written back to the same table. FileCount reads from and writes to Accumulo. This requires scan authorizations for the read and a visibility for the data written. In this example, the authorizations and visibility are set to the same value, exampleVis. See README.visibility for more information on visibility and authorizations. -$ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.FileCount instance zookeepers username password dirTable exampleVis exampleVis +$ ./bin/accumulo org.apache.accumulo.examples.simple.dirlist.FileCount -i instance -z zookeepers -u username -p password -t dirTable --auths exampleVis
svn commit: r893383 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Thu Jan 9 02:58:28 2014
New Revision: 893383
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 9 02:58:28 2014
@@ -1 +1 @@
-1556070
+1556702
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Thu Jan 9 02:58:28 2014
@@ -145,6 +145,7 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
Aaron Glahehttp://www.data-tactics.com/>Data TaticsET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Alex Moundalexishttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ Arshak Navruzyan
Chris Bennight
Chris McCubbinhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Christian Rohlinghttp://endgame.com/>EndgameET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r893385 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Thu Jan 9 03:00:11 2014
New Revision: 893385
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 9 03:00:11 2014
@@ -1 +1 @@
-1556702
+1556704
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Thu Jan 9 03:00:11 2014
@@ -145,7 +145,7 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
Aaron Glahehttp://www.data-tactics.com/>Data TaticsET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Alex Moundalexishttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
- Arshak Navruzyan
+ Arshak Navruzyanhttp://www.argyledata.com/";>Argyle Data
Chris Bennight
Chris McCubbinhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Christian Rohlinghttp://endgame.com/>EndgameET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r893606 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Fri Jan 10 19:32:28 2014
New Revision: 893606
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 10 19:32:28 2014
@@ -1 +1 @@
-1556704
+1557233
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Fri Jan 10 19:32:28 2014
@@ -136,7 +136,7 @@ tr:nth-child(2n+1) {
vinesJohn Vineshttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
elserjJosh Elserhttp://hortonworks.com/>HortonworksET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
kturnerKeith Turnerhttp://www.ptech-llc.com/>Peterson TechnologiesET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
- mdrobMike Drobhttp://www.cloudera.com";>ClouderaPT (http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>-8
/ http://www.timeanddate.com/library/abbreviations/timezones/na/pdt.html>-7)
+ mdrobMike Drobhttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
ujustgotbilldWilliam Slacumhttp://www.koverse.com";>KoverseET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r894148 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Tue Jan 14 20:04:21 2014
New Revision: 894148
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan 14 20:04:21 2014
@@ -1 +1 @@
-1557233
+1558179
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Tue Jan 14 20:04:21 2014
@@ -192,6 +192,7 @@ tr:nth-child(2n+1) {
Tim Halloran
Tim Reardon
Travis Pinney
+ Vikram Srivastavahttp://www.cloudera.com";>ClouderaPT (http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>-8
/ http://www.timeanddate.com/library/abbreviations/timezones/na/pdt.html>-7)
svn commit: r894216 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Wed Jan 15 05:10:49 2014
New Revision: 894216
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 15 05:10:49 2014
@@ -1 +1 @@
-1558179
+1558294
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Wed Jan 15 05:10:49 2014
@@ -137,6 +137,7 @@ tr:nth-child(2n+1) {
elserjJosh Elserhttp://hortonworks.com/>HortonworksET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
kturnerKeith Turnerhttp://www.ptech-llc.com/>Peterson TechnologiesET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
mdrobMike Drobhttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ busbeySean Busbeyhttp://www.cloudera.com";>ClouderaCT (http://www.timeanddate.com/library/abbreviations/timezones/na/cst.html>-6
/ http://www.timeanddate.com/library/abbreviations/timezones/na/cdt.html>-5)
ujustgotbilldWilliam Slacumhttp://www.koverse.com";>KoverseET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
@@ -183,8 +184,7 @@ tr:nth-child(2n+1) {
Ryan Fishelhttp://www.cloudera.com";>Cloudera
Ryan Leary
Sapah Shah
- Scott Kuehn
- Sean Busbeyhttp://www.cloudera.com";>ClouderaCT (http://www.timeanddate.com/library/abbreviations/timezones/na/cst.html>-6
/ http://www.timeanddate.com/library/abbreviations/timezones/na/cdt.html>-5)
+ Scott Kuehn
Sean Hickey
stevelSteve Loughranhttp://hortonworks.com/>Hortonworks(http://www.timeanddate.com/library/abbreviations/timezones/eu/gmt.html>0
/ http://www.timeanddate.com/library/abbreviations/timezones/eu/bst.html>+1)
supunSupun Kamburugamuva
svn commit: r894219 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Author: buildbot Date: Wed Jan 15 05:29:26 2014 New Revision: 894219 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/governance/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Jan 15 05:29:26 2014 @@ -1 +1 @@ -1558294 +1558295 Modified: websites/staging/accumulo/trunk/content/governance/releasing.html == --- websites/staging/accumulo/trunk/content/governance/releasing.html (original) +++ websites/staging/accumulo/trunk/content/governance/releasing.html Wed Jan 15 05:29:26 2014 @@ -121,13 +121,39 @@ Once testing is deemed successful and documentation is complete, move on to Releasing. Testing +Testing for an Accumulo release includes a few steps that a developer may take without a Hadoop cluster and several that require a working cluster. +Stand alone +The following steps can be taken without having an underlying cluster. They SHOULD be handled with each Hadoop profile available for a given release version. To activate an alternative profile specify e.g. "-Dhadoop.profile=2" for the Hadoop 2 profile on the Maven commandline. Some older versions of Accumulo referred to Hadoop profiles diferently; see the README that came with said versions for details on building against different Hadoop versions. -All JUnit tests must pass. This should be a requirement of any patch so it should never be an issue of the codebase. -All functional tests must complete successfully. +All JUnit tests must pass. This should be a requirement of any patch so it should never be an issue of the codebase. +Use "mvn package" to run against the default profile of a particular release +Use "mvn -Dhadoop.profile=2 package" to test against the Hadoop 2 profile on e.g. 1.4 or 1.5 +Use "mvn -Dhadoop.profile=1 package" to test against the Hadoop 1 profile on e.g. 1.6 or later + + Analyze output of static analysis tools like Findbugs and PMD. -Two 24-hour periods of the randomwalk LongClean test with and without agitation need to be run successfully on a cluster. -Two 24-hour periods of continuous ingest with and without agitation need to be validated successfully on a cluster. -Two 72-hour periods of continuous ingest with and without agitation on a cluster. No validation is necessary but the cluster should be checked to ensure it is still functional. +For versions 1.6 and later, all functional tests must pass via the Maven failsafe plugin. +Use "mvn verify" to run against the default profile of a particular release +Use "mvn -Dhadoop.profile=1 verify" to run the functional tests against the Hadoop 1 profile + + + +Cluster based +The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node in psuedo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base will be exercised. For the purposes of release testing, you should note the number of nodes and versions used. See the Releasing section for more details. + +For versions prior to 1.6, all functional tests must complete successfully. +See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests. + + +Two 24-hour periods of the randomwalk LongClean test with and without agitation need to be run successfully. +See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean module. + + +Two 24-hour periods of continuous ingest with and without agitation need to be validated successfully. +See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying the continous ingest test. + + +Two 72-hour periods of continuous ingest with and without agitation. No validation is necessary but the cluster should be checked to ensure it is still functional. Releasing @@ -137,7 +163,10 @@ PGP Signatures of the tarball must be signed to a separate file and made available in the public_html folder of the user creating the release on people.apache.org, along with the tarball and MD5 and SHA512 checksums. -A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release; at least 3 +1 votes from PMC members are required. All checksums and signatures need to be verified before any voter can +1 it. Voting shall last 72 hours. +A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release; at least 3 +1 votes from PMC members are required. All checksums and signatures need to be verified before any voter can +1 it. Voting shall last 72 hours. +Voters SHOULD include with their v
svn commit: r894292 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Author: buildbot Date: Wed Jan 15 15:45:13 2014 New Revision: 894292 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/governance/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Jan 15 15:45:13 2014 @@ -1 +1 @@ -1558295 +1558437 Modified: websites/staging/accumulo/trunk/content/governance/releasing.html == --- websites/staging/accumulo/trunk/content/governance/releasing.html (original) +++ websites/staging/accumulo/trunk/content/governance/releasing.html Wed Jan 15 15:45:13 2014 @@ -164,7 +164,7 @@ PGP Signatures of the tarball must be signed to a separate file and made available in the public_html folder of the user creating the release on people.apache.org, along with the tarball and MD5 and SHA512 checksums. A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release; at least 3 +1 votes from PMC members are required. All checksums and signatures need to be verified before any voter can +1 it. Voting shall last 72 hours. -Voters SHOULD include with their vote details on the tests from the testing section they have successfully run. If given, said details for each test MUST include: the number of worker nodes in the cluster, the operating system and version, the Hadoop version, and the Zookeeper version. All such gathered testing information will be included in the release notes. +Voters SHOULD include with their vote details on the tests from the testing section they have successfully run. If given, said details for each test MUST include: the number of worker nodes in the cluster, the operating system and version, the Hadoop version, and the Zookeeper version. For testing done on a version other than the release candidate that is deemed relevant, include the commit hash. All such gathered testing information will be included in the release notes. Upon successful vote, the new releases can be retagged to remove the RC status and released on the Accumulo webpage.
svn commit: r895248 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html
Author: buildbot Date: Thu Jan 23 18:51:47 2014 New Revision: 895248 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/downloads/index.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Jan 23 18:51:47 2014 @@ -1 +1 @@ -1558437 +1560781 Modified: websites/staging/accumulo/trunk/content/downloads/index.html == --- websites/staging/accumulo/trunk/content/downloads/index.html (original) +++ websites/staging/accumulo/trunk/content/downloads/index.html Thu Jan 23 18:51:47 2014 @@ -113,7 +113,7 @@ For convenience, http://www.apa Documentation -https://svn.apache.org/repos/asf/accumulo/tags/1.5.0/README onClick="javascript: _gaq.push(['_trackPageview', '/1.5/README']);">README +https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=README;hb=5266a71be09772d58a3cce223fdc61192097c339 onClick="javascript: _gaq.push(['_trackPageview', '/1.5/README']);">README pdf manual html manual javadoc
svn commit: r897921 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Author: buildbot Date: Fri Feb 14 17:14:32 2014 New Revision: 897921 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Feb 14 17:14:32 2014 @@ -1 +1 @@ -1567814 +1568360 Modified: websites/staging/accumulo/trunk/content/releasing.html == --- websites/staging/accumulo/trunk/content/releasing.html (original) +++ websites/staging/accumulo/trunk/content/releasing.html Fri Feb 14 17:14:32 2014 @@ -95,7 +95,7 @@ Setup There are number of things that are required before attempting to build a release. -Use gpg-agent, be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build as it will cause things to fail. If you do not have a GPG key, reference the very thorough https://www.apache.org/dev/release-signing";>ASF release signing documentation +Use gpg-agent, be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build as it will cause things to fail. For example, you can add default-cache-ttl 6000 to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough https://www.apache.org/dev/release-signing";>ASF release signing documentation Make sure the system you're using is able to creation RPMs and DEBs. Ensure that you're using the correct major release of Java (check javadoc too). Ensure that you're building Apache Accumulo with a username that has the same name as your Apache ID (this is due to
svn commit: r898428 - in /websites/staging/accumulo/trunk/content: ./ notable_features.html
Author: buildbot Date: Tue Feb 18 20:10:40 2014 New Revision: 898428 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/notable_features.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Feb 18 20:10:40 2014 @@ -1 +1 @@ -1568360 +1569514 Modified: websites/staging/accumulo/trunk/content/notable_features.html == --- websites/staging/accumulo/trunk/content/notable_features.html (original) +++ websites/staging/accumulo/trunk/content/notable_features.html Tue Feb 18 20:10:40 2014 @@ -130,7 +130,7 @@ documents containing certain words. Multiple masters can be configured. Zookeeper locks are used to determine which master is active. The remaining masters simply wait for the current master to lose its lock. Current master state is held in the metadata table -and Zookeeper (see FATE). +and Zookeeper (see FATE). Write ahead log In version 1.4, tablet servers send mutations to loggers which write to the local file system, not HDFS. Each mutation is written to multiple loggers, before being committed. In normal configurations, loggers
svn commit: r898544 - in /websites/staging/accumulo/trunk/content: ./ contrib.html
Author: buildbot Date: Wed Feb 19 16:06:58 2014 New Revision: 898544 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/contrib.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Feb 19 16:06:58 2014 @@ -1 +1 @@ -1569514 +1569805 Modified: websites/staging/accumulo/trunk/content/contrib.html == --- websites/staging/accumulo/trunk/content/contrib.html (original) +++ websites/staging/accumulo/trunk/content/contrib.html Wed Feb 19 16:06:58 2014 @@ -97,17 +97,17 @@ Each of the below contrib project handles their own development and release cycle. For information on what version(s) of Accumulo they work with, see the documentation for the individual project. Instamo Archetype A Maven Archetype that automates the customization of Instamo to quickly spin up an Accumulo process in memory. -The Apache Accumulo Instamo Archetype uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-instamo-archetype.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-instamo-archetype.git";>checkout). It builds with [Apache Maven][maven]. See the section on contributing for instructions on submitting issues and patches. +The Apache Accumulo Instamo Archetype uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-instamo-archetype.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-instamo-archetype.git";>checkout). It builds with http://maven.apache.org/";>Apache Maven. See the section on contributing for instructions on submitting issues and patches. Wikisearch Application A complex application example that makes use of most of the Accumulo feature stack. The Wikisearch application provides an example of indexing and querying Wikipedia data within Accumulo. It is a great place to start if you want to get familiar with good development practices building on Accumulo. For details on setting up the application, see the project's README. You can also read an overview and some performance numbers. -The Apache Accumulo Wikisearch Example uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-wikisearch.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-wikisearch.git";>checkout). It builds with [Apache Mave][maven]. See the section on contributing for instructions on submitting issues and patches. +The Apache Accumulo Wikisearch Example uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-wikisearch.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-wikisearch.git";>checkout). It builds with http://maven.apache.org/";>Apache Maven. See the section on contributing for instructions on submitting issues and patches. Pig Support A storage module for http://pig.apache.org/";>Pig allows users to use an Accumulo as either a source or a sink when writing analytics in the Pig scripting language. For details on which Pig version(s) are required to run the storage module, see the project details. -The Apache Accumulo Pig Module uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-pig.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-pig.git";>checkout). It builds with [Apache Maven][maven]. See the section on contributing for instructions on submitting issues and patches. +The Apache Accumulo Pig Module uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-pig.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-pig.git";>checkout). It builds with http://maven.apache.org/";>Apache Maven. See the section on contributing for instructions on submitting issues and patches. Hama Integration An implementation for running http://hama.apache.org/hama_bsp_tutorial.html";>Bulk Synchronous Parallel (BSP) algorithms implemented via http://hama.apache.org/";>Apache Hama on top of data stored in Accumulo. -The Apache Accumulo BSP implementation uses http://git-scm.com/";>Git version control (https://git-wip-us.apache.org/repos/asf?p=accumulo-bsp.git;a=summary";>browse|https://git-wip-us.apache.org/repos/asf/accumulo-bsp.git";>checkout). It builds with [Apache Mave][maven]. See the section on contributing for instructions on submitting issues and patches. +The Apache Accumulo BSP imple
svn commit: r899046 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Author: buildbot Date: Mon Feb 24 19:08:21 2014 New Revision: 899046 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Mon Feb 24 19:08:21 2014 @@ -1 +1 @@ -1569805 +1571400 Modified: websites/staging/accumulo/trunk/content/releasing.html == --- websites/staging/accumulo/trunk/content/releasing.html (original) +++ websites/staging/accumulo/trunk/content/releasing.html Mon Feb 24 19:08:21 2014 @@ -144,6 +144,12 @@ choose), and fix what needs fixing. If the vote passes, huzzah, you're almost done. All you need to do is to promote that stage repository using Nexus which you can do with the click of a button. These will trigger a process to get the release out to all of the mirrors. +Update the Website +After a successful vote, this website needs to be updated with the new artifacts. The downloads page should +be updated with the new information. A new minor release should replace the previous minor release in the major +version. The Javadocs should be updated, with special care being taken to ensure that Javadocs are http://www.kb.cert.org/vuls/id/225657";>patched before +uploading as long as Java 6 is the version targeted by Accumulo (with greater than Java 7u21 being used once we +switch to Java7). The user manual should also be updated if changes were made to it. References Some good references that explain a few things:
svn commit: r899217 - in /websites/staging/accumulo/trunk/content: ./ source.html
Author: buildbot Date: Wed Feb 26 03:46:46 2014 New Revision: 899217 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/source.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Feb 26 03:46:46 2014 @@ -1 +1 @@ -1571400 +1571905 Modified: websites/staging/accumulo/trunk/content/source.html == --- websites/staging/accumulo/trunk/content/source.html (original) +++ websites/staging/accumulo/trunk/content/source.html Wed Feb 26 03:46:46 2014 @@ -130,9 +130,11 @@ need to install or modify the Thrift def For older branches, "mvn package && mvn assembly:single" may be required instead, and the tar will be built in the target directory. Continuous Integration Accumulo uses http://jenkins-ci.org/";>Jenkins for automatic builds. -https://builds.apache.org/job/Accumulo-Trunk/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-Trunk/";>Trunk -https://builds.apache.org/job/Accumulo-1.4.x/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.5.x/";>1.5 Branch -https://builds.apache.org/job/Accumulo-1.4.x/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.4.x/";>1.4 Branch +https://builds.apache.org/job/Accumulo-Master/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-Master/";>Master +https://builds.apache.org/job/Accumulo-1.6/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.6/";>1.6 Branch +https://builds.apache.org/job/Accumulo-1.5-Hadoop-2/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.5-Hadoop-2/";>1.5 Branch (Hadoop 2) +https://builds.apache.org/job/Accumulo-1.5/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.5/";>1.5 Branch (Hadoop 1) +https://builds.apache.org/job/Accumulo-1.4/lastBuild/buildStatus"; width=18> https://builds.apache.org/job/Accumulo-1.4/";>1.4 Branch Issue Tracking Accumulo https://issues.apache.org/jira/browse/accumulo";>tracks issues with http://www.atlassian.com/software/jira/overview";>JIRA. Every commit should reference a JIRA ticket of the form ACCUMULO-#. Merging Practices
svn commit: r899346 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Author: buildbot Date: Thu Feb 27 02:45:27 2014 New Revision: 899346 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Feb 27 02:45:27 2014 @@ -1 +1 @@ -1571905 +1572413 Modified: websites/staging/accumulo/trunk/content/releasing.html == --- websites/staging/accumulo/trunk/content/releasing.html (original) +++ websites/staging/accumulo/trunk/content/releasing.html Thu Feb 27 02:45:27 2014 @@ -105,6 +105,14 @@ Have a clean workspace before starting. Given all of this, it's recommended that you only attempt making a release from a GNU/Linux machine. +Update CHANGES +The CHANGES file should, at a minimum, contain all Jira completed issues from the current "major" release line +(e.g. for 1.5.2, CHANGES would contain 1.5.2, 1.5.1 and 1.5.0 Jira issues). Issues that did not +result in an actual change (e.g. "Duplicate", "Invalid", "Won't Fix" resolutions) should not be included +in the file. The changes should be ordered by version number in descending order, grouped by Jira +issue type. There is still disagreement if issues from all previous versions that are contained in +the present version should be listed (including issues from former major releases); as of 1.5.1, +it was agreed upon to omit issues from previous major versions. Create the candidate You should use the provided script assemble/build.sh to create the release candidate. This script is desirable as it activates all necessary maven profiles in addition to verifying that certain preconditions
svn commit: r899879 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Author: buildbot Date: Mon Mar 3 16:48:08 2014 New Revision: 899879 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Mon Mar 3 16:48:08 2014 @@ -1 +1 @@ -1572413 +1573608 Modified: websites/staging/accumulo/trunk/content/releasing.html == --- websites/staging/accumulo/trunk/content/releasing.html (original) +++ websites/staging/accumulo/trunk/content/releasing.html Mon Mar 3 16:48:08 2014 @@ -95,8 +95,8 @@ Setup There are number of things that are required before attempting to build a release. -Use gpg-agent, be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build as it will cause things to fail. For example, you can add default-cache-ttl 6000 to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough https://www.apache.org/dev/release-signing";>ASF release signing documentation -Make sure the system you're using is able to creation RPMs and DEBs. +Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build, as it will cause things to fail. For example, you can add default-cache-ttl 6000 to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough https://www.apache.org/dev/release-signing";>ASF release signing documentation. +Make sure the system you're using is able to create RPMs and DEBs. Ensure that you're using the correct major release of Java (check javadoc too). Ensure that you're building Apache Accumulo with a username that has the same name as your Apache ID (this is due to the maven-release-plugin and staging the release candidate). @@ -117,26 +117,26 @@ it was agreed upon to omit issues from p You should use the provided script assemble/build.sh to create the release candidate. This script is desirable as it activates all necessary maven profiles in addition to verifying that certain preconditions are met, like RPM signing availablilty and the ability to sign files using GPG. The --test option can -be used as a dry-run to creating a release candidate. The --create-release-candidate option should be -provided to create the actual release candidate. +be used as a dry run for creating a release candidate. The --create-release-candidate option should be +used to create the actual release candidate. When invoking build.sh with the --create-release-candidate option, the majority of the work will be performed -by the maven-release-plugin, invoking release:clean, release:prepare, and release:perform. These will +by the maven-release-plugin, invoking release:clean, release:prepare, and release:perform. These will guide you through choosing the correct versions. The default options provided should be what you choose. -It is highly recommended that an 'RC' suffix is not appended to the release version the the plugin prompts -you for as that will result in that version string being placed into the poms which then would require +It is highly recommended that an 'RC' suffix is not appended to the release version the plugin prompts +you for, as that will result in that version string being placed into the poms, which then would require voting to occur on artifacts that cannot be directly promoted. After the build.sh script finishes (this will likely take at least 15 minutes, even on recent hardware), your current branch will be on the "next" version that you provided to the release plugin. -Likely, this process will actually fail because the maven-release-plugin is not configured to push to the -remote repository automatically, and thus, will fail; however, this is (semi-)expected. At this point, you -should have a local git-tag for the release that you're creating. At this point, you should create a branch +This process is likely to fail because the maven-release-plugin is not configured to push to the +remote repository automatically; however, this is (semi-)expected. At this point, you +should have a local git tag for the release that you're creating. You should create a branch from the tag that was made by the release plugin which includes the -rcN suffix. This way, the branch name -will correctly identify which release-candidate this is, while the contents of that tag will have the correct +will correctly identify which release
svn commit: r900135 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot
Date: Wed Mar 5 16:44:16 2014
New Revision: 900135
Log:
Staging update by buildbot for accumulo
Added:
websites/staging/accumulo/trunk/content/bylaws.html
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 5 16:44:16 2014
@@ -1 +1 @@
-1573608
+1574568
Added: websites/staging/accumulo/trunk/content/bylaws.html
==
--- websites/staging/accumulo/trunk/content/bylaws.html (added)
+++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 5 16:44:16 2014
@@ -0,0 +1,223 @@
+http://www.w3.org/TR/html4/loose.dtd";>
+
+
+
+
+ Apache Accumulo Bylaws
+
+
+
+
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-21103458-6']);
+_gaq.push(['_setDomainName', 'apache.org']);
+_gaq.push(['_setAllowLinker', true]);
+_gaq.push(['_trackPageview']);
+
+(function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript';
ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? '<a rel="nofollow" href="https://ssl">https://ssl</a>' :
'<a rel="nofollow" href="http://www">http://www</a>') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+})();
+
+
+
+
+
+
+
+
+
+
+
+ Project
+
+Home
+Downloads
+Features
+http://www.apache.org/licenses/LICENSE-2.0";>License
+
+Community
+
+Get Involved
+Mailing Lists
+People
+
+Development
+
+Source & Guide
+Git WIP
+Contrib Projects
+Making Releases
+https://issues.apache.org/jira/browse/accumulo";>Issues
+https://builds.apache.org/view/A-D/view/Accumulo/";>Builds
+
+Documentation
+
+Manual 1.4 / 1.5
+Javadoc 1.4 / 1.5
+Examples 1.4 / 1.5
+Screenshots
+Papers & Other Links
+Glossary
+
+ASF links
+
+http://www.apache.org";>Apache Software Foundation
+http://www.apache.org/foundation/sponsorship.html";>Sponsorship
+http://www.apache.org/security/";>Security
+http://www.apache.org/foundation/thanks.html";>Thanks
+
+
+
+
+™
+
+
+
+Apache Accumulo Bylaws
+Apache Accumulo Project Bylaws
+This is version 0 of the bylaws. This draft has not yet been accepted by
the Accumulo Project and only exists for voting purposes.
+Introduction
+This document defines the bylaws under which the Apache Accumulo project
operates. It defines the roles and responsibilities of the project, who may
vote, how voting works, how conflicts are resolved, etc.
+Accumulo is a project of the http://www.apache.org/foundation/";>Apache Software Foundation. The
foundation holds the copyright on Apache code including the code in the
Accumulo codebase. The http://www.apache.org/foundation/faq.html";>foundation FAQ explains
the operation and background of the foundation.
+Accumulo is typical of Apache projects in that it operates under a set of
principles, known collectively as the Apache Way. If you are new to Apache
development, please refer to the http://incubator.apache.org/";>Incubator project for more information
on how Apache projects operate. Terms used at the ASF are defined in the http://www.apache.org/foundation/glossary.html";>ASF glossary.
+Roles and Responsibilities
+Apache projects define a set of roles with associated rights and
responsibilities. These roles govern what tasks an individual may perform
within the project. The roles are defined in the following sections.
+Users
+The most important participants in the project are people who use our
software. The majority of our contributors start out as users and guide their
development efforts from the user's perspective.
+Users contribute to the Apache projects by providing feedback to
contributors in the form of bug reports and feature suggestions. As well, users
participate in the Apache community by helping other users on mailing lists and
user support forums.
+Contributors
+All of the volunteers who are contributing time, code, documentation, or
resources to the Accumulo project are considered contributors. A contributor
that makes sustained, welcome contributions to the project may be invited to
become a committer, though the exact timing of such invitations depends on many
factors.
+Committers
+The project's committers are responsible for the project's technical
management. Committers have write access to the project's code repositories and
may cast binding votes on any technical discussion regarding Accumulo.
Comm
svn commit: r900138 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Wed Mar 5 17:08:14 2014 New Revision: 900138 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 5 17:08:14 2014 @@ -1 +1 @@ -1574568 +1574574 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 5 17:08:14 2014 @@ -112,12 +112,14 @@ It is the custom of the Accumulo project to also invite each committer to become a member of the Accumulo PMC. Project Management Committee The Project Management Committee (PMC) is responsible to the ASF Board of Directors (âthe Boardâ) for the management and oversight of the Apache Accumulo codebase. The responsibilities of the PMC include: -Deciding what is distributed as products of the Apache Accumulo project. In particular all releases must be approved by the PMC. -Maintaining the project's shared resources, including the codebase repository, mailing lists, and websites. -Speaking on behalf of the project. -Resolving license disputes regarding products of the project. -Nominating new PMC members and committers. -Maintaining these bylaws and other guidelines of the project. + +Deciding what is distributed as products of the Apache Accumulo project. In particular all releases must be approved by the PMC. +Maintaining the project's shared resources, including the codebase repository, mailing lists, and websites. +Speaking on behalf of the project. +Resolving license disputes regarding products of the project. +Nominating new PMC members and committers. +Maintaining these bylaws and other guidelines of the project. + Membership of the PMC is by invitation only and must be approved by a consensus approval of active PMC members. Upon acceptance of the invitation to become a PMC member, it is the accepting memberâs responsibility to update his/her status on the Accumulo web page accordingly. A PMC member is considered emeritus, meaning inactive, by his or her own declaration or by not contributing in any form to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update his/her status on the web page accordingly. The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (Vice President, Apache Accumulo) and has primary responsibility to the board for the management of the projects within the scope of the Accumulo PMC. The chair reports to the board quarterly on developments within the Accumulo project.
svn commit: r900148 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Wed Mar 5 18:45:05 2014 New Revision: 900148 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 5 18:45:05 2014 @@ -1 +1 @@ -1574574 +1574612 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 5 18:45:05 2014 @@ -91,8 +91,7 @@ Apache Accumulo Bylaws -Apache Accumulo Project Bylaws -This is version 0 of the bylaws. This draft has not yet been accepted by the Accumulo Project and only exists for voting purposes. +This is version 0 of the bylaws. This draft has not yet been accepted by the Accumulo Project and only exists for voting purposes. Introduction This document defines the bylaws under which the Apache Accumulo project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc. Accumulo is a project of the http://www.apache.org/foundation/";>Apache Software Foundation. The foundation holds the copyright on Apache code including the code in the Accumulo codebase. The http://www.apache.org/foundation/faq.html";>foundation FAQ explains the operation and background of the foundation. @@ -108,18 +107,30 @@ The project's committers are responsible for the project's technical management. Committers have write access to the project's code repositories and may cast binding votes on any technical discussion regarding Accumulo. Committer access is by invitation only and must be approved by consensus approval of the active PMC members. Upon acceptance of the invitation to become a committer, it is the accepting memberâs responsibility to update his/her status on the Accumulo web page accordingly. A committer is considered emeritus, meaning inactive, by his or her own declaration or by not reviewing patches or committing patches to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update his/her status on the web page accordingly. An emeritus committerâs commit access may be disabled as part of routine security. Access shall not be removed without notifying the committer, and access shall be maintained if the committer wishes to leave it active. A committerâs commit access shall be reactivated upon the committerâs request to the PMC. -All Apache committers are required to have a signed http://www.apache.org/licenses/icla.txt";>Contributor License Agreement on file with the Apache Software Foundation. There is a http://www.apache.org/dev/committers.html";>Committer FAQ which provides more details on the requirements for committers. +All Apache committers are required to have a signed http://www.apache.org/licenses/icla.txt";>Contributor License Agreement (CLA) on file with the Apache Software Foundation. Under the terms of the CLA that all committers must sign, a committer's primary responsibility is to ensure that all code committed to Apache Accumulo is licensed appropriately and meets those criteria set forth in the CLA (including both original works and patches committed on behalf of other contributors). There is a http://www.apache.org/dev/committers.html";>Committer FAQ which provides more details on the requirements for committers. It is the custom of the Accumulo project to also invite each committer to become a member of the Accumulo PMC. Project Management Committee -The Project Management Committee (PMC) is responsible to the ASF Board of Directors (âthe Boardâ) for the management and oversight of the Apache Accumulo codebase. The responsibilities of the PMC include: +The role of the PMC from a Foundation perspective is http://apache.org/foundation/how-it-works.html#pmc";>oversight. The main +role of the PMC is not code and not coding - but to ensure that all legal +issues are addressed, that procedure is followed, and that each and every +release is the product of the community as a whole. That is key to our +litigation protection mechanisms. +Secondly the role of the PMC is to further the long term development and +health of the community as a whole, and
svn commit: r900149 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Wed Mar 5 18:46:03 2014 New Revision: 900149 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 5 18:46:03 2014 @@ -1 +1 @@ -1574612 +1574615 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 5 18:46:03 2014 @@ -171,7 +171,7 @@ stability, and robustness of both code a A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid. If you disagree with a valid veto, you must lobby the person casting the veto to withdraw his or her veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in a timely manner. Actions -This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in business days. In general votes should not be called at times when it is known that interested members of the project will be unavailable. +This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in days. In general votes should not be called at times when it is known that interested members of the project will be unavailable. Action Description
svn commit: r900309 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html
Author: buildbot Date: Thu Mar 6 16:43:13 2014 New Revision: 900309 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/downloads/index.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 16:43:13 2014 @@ -1 +1 @@ -1574615 +1574955 Modified: websites/staging/accumulo/trunk/content/downloads/index.html == --- websites/staging/accumulo/trunk/content/downloads/index.html (original) +++ websites/staging/accumulo/trunk/content/downloads/index.html Thu Mar 6 16:43:13 2014 @@ -91,30 +91,30 @@ Apache Accumulo Downloads -1.5.0 (latest) -The most recent Apache Accumulo™ release is version 1.5.0. See the https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=5266a71be09772d58a3cce223fdc61192097c339"; title="1.5.0 Release Notes">Release Notes. +1.5.1 (latest) +The most recent Apache Accumulo™ release is version 1.5.1. See the https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=3478f71ae888f8d73aaa93837319a6dbb4ba0c8a"; title="1.5.1 CHANGES">CHANGES. Be sure to verify your downloads by these http://www.apache.org/info/verification.html"; title="Verify">procedures using these http://www.apache.org/dist/accumulo/KEYS"; title="KEYS">KEYS. -For convenience, http://www.apache.org/dist/accumulo/1.5.0/MD5SUM";>MD5 and http://www.apache.org/dist/accumulo/1.5.0/SHA1SUM";>SHA1 hashes are also available. +For convenience, http://www.apache.org/dist/accumulo/1.5.1/MD5SUM";>MD5 and http://www.apache.org/dist/accumulo/1.5.1/SHA1SUM";>SHA1 hashes are also available. Generic Binaries -accumulo-1.5.0-bin.tar.gz http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-bin.tar.gz onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-bin.tar.gz']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-bin.tar.gz.asc";>gpg signature) +accumulo-1.5.1-bin.tar.gz http://www.apache.org/dyn/closer.cgi/accumulo/1.5.1/accumulo-1.5.1-bin.tar.gz onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.1-bin.tar.gz']);">mirrors (http://www.apache.org/dist/accumulo/1.5.1/accumulo-1.5.1-bin.tar.gz.asc";>gpg signature) Platform Binaries -accumulo-1.5.0-bin.rpm http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-bin.rpm onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-bin.rpm']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-bin.rpm.asc";>gpg signature) -accumulo-1.5.0-native.rpm http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-native.rpm onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-native.rpm']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-native.rpm.asc";>gpg signature) -accumulo-1.5.0-test.rpm http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-test.rpm onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-test.rpm']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-test.rpm.asc";>gpg signature) -accumulo-1.5.0-bin.deb http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-bin.deb onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-bin.deb']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-bin.deb.asc";>gpg signature) -accumulo-1.5.0-native.deb http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-native.deb onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-native.deb']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-native.deb.asc";>gpg signature) -accumulo-1.5.0-test.deb http://www.apache.org/dyn/closer.cgi/accumulo/1.5.0/accumulo-1.5.0-test.deb onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.0-test.deb']);">mirrors (http://www.apache.org/dist/accumulo/1.5.0/accumulo-1.5.0-test.deb.asc";>gpg signature) +accumulo-1.5.1-bin.rpm http://www.apache.org/dyn/closer.cgi/accumulo/1.5.1/accumulo-1.5.1-bin.rpm onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.5.1-bin.rpm']);">mirrors (http://www.apache.org/dist/accumulo/1.5.1/
svn commit: r900317 - in /websites/staging/accumulo/trunk/content: ./ release_notes/ release_notes/1.5.1_release_notes.md
Author: buildbot Date: Thu Mar 6 17:51:09 2014 New Revision: 900317 Log: Staging update by buildbot for accumulo Added: websites/staging/accumulo/trunk/content/release_notes/ websites/staging/accumulo/trunk/content/release_notes/1.5.1_release_notes.md Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 17:51:09 2014 @@ -1 +1 @@ -1574955 +1574979 Added: websites/staging/accumulo/trunk/content/release_notes/1.5.1_release_notes.md == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1_release_notes.md (added) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1_release_notes.md Thu Mar 6 17:51:09 2014 @@ -0,0 +1,89 @@ +Title: Apache Accumulo 1.5.1 Release Notes +Notice:Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + . + http://www.apache.org/licenses/LICENSE-2.0 + . + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +## Accumulo 1.5.1 Release Notes (Work in progress) + + +### Notable Improvements + +Accumulo client code creates background threads that users can not stop. This +causes problems when using Accumulo with Tomcat or JBoss. [ACCUMULO-2128][3] +introduced the static utility org.apache.accumulo.core.util.CleanUp to clean +these threads up. + +If IPv6 is enabled on nodes but not in use on the network, then Accumulo may +have issues communicating with itself. [ACCUMULO-2262][4] adds java +configuration to startup scripts to prefer IPv4. + +[ACCUMULO-1933][7] allows lower case memory units in Accumulo configuration. + +[ACCUMULO-2360][14] allows users to configure the maximum frame size an +Accumulo server will read. This prevents non Accumulo client from connecting +and causing memory exhaustion. + +The following documentation updates were made : [ACCUMULO-2127][17], +[ACCUMULO-1956][18], and [ACCUMULO-1428][19]. + +### Notable Bug Fixes + + * [ACCUMULO-1800][5] fixed deletes made via the Proxy. + * [ACCUMULO-1994][6] fixed ranges in the Proxy. + * [ACCUMULO-2234][8] fixed offline map reduce over non default HDFS location + * [ACCUMULO-1615][15] fixed service accumulo-tserver stop + * [ACCUMULO-1876][16] fixed issues with ivy + +Some important internal bugs were fixed in Accumulo that should be considered +when deciding to upgrade. These bugs are : [ACCUMULO-2057][9], +[ACCUMULO-2261][10], [ACCUMULO-2037][11], [ACCUMULO-1821][12], +[ACCUMULO-1572][13], [ACCUMULO-2078][20], [ACCUMULO-1985][21], +[ACCUMULO-1999][22],[ACCUMULO-2065][23], and [ACCUMULO-1630][24]. + + +### Known Issues + +When using Accumulo 1.5 and Hadoop 2, Accumulo will call hsync() on hdfs. +Calling hsync improves durability by ensuring data is on disk, however calling +it frequently slows writes. A work around is to increase +tserver.mutation.queue.max. See [ACCUMULO-1905 comment][1], [ACCUMULO-1950][2], and +the new tserver.mutation.queue.max documentation for more information. + + +[1]: https://issues.apache.org/jira/browse/ACCUMULO-1905?focusedCommentId=13915208&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13915208 +[2]: https://issues.apache.org/jira/browse/ACCUMULO-1950 +[3]: https://issues.apache.org/jira/browse/ACCUMULO-2128 +[4]: https://issues.apache.org/jira/browse/ACCUMULO-2262 +[5]: https://issues.apache.org/jira/browse/ACCUMULO-1800 +[6]: https://issues.apache.org/jira/browse/ACCUMULO-1994 +[7]: https://issues.apache.org/jira/browse/ACCUMULO-1933 +[8]: https://issues.apache.org/jira/browse/ACCUMULO-2234 +[9]: https://issues.apache.org/jira/browse/ACCUMULO-2057 +[10]: https://issues.apache.org/jira/browse/ACCUMULO-2261 +[11]: https://issues.apache.org/jira/browse/ACCUMULO-2037 +[12]: https://issues.apache.org/jira/browse/ACCUMULO-1821 +[13]: https://issues.apache.org/jira/browse/ACCUMULO-1572 +[14]: https://issues.apache.org/jira/browse/ACCUMULO-2360 +[15]: https://issues.apache.org/jira/browse/ACCUMULO-1615 +[16]: https://issues.apache.org/jira/b
svn commit: r900318 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1_release_notes.md release_notes/release_notes.html
Author: buildbot
Date: Thu Mar 6 17:52:15 2014
New Revision: 900318
Log:
Staging update by buildbot for accumulo
Added:
websites/staging/accumulo/trunk/content/release_notes/release_notes.html
Removed:
websites/staging/accumulo/trunk/content/release_notes/1.5.1_release_notes.md
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 6 17:52:15 2014
@@ -1 +1 @@
-1574979
+1574980
Added: websites/staging/accumulo/trunk/content/release_notes/release_notes.html
==
--- websites/staging/accumulo/trunk/content/release_notes/release_notes.html
(added)
+++ websites/staging/accumulo/trunk/content/release_notes/release_notes.html
Thu Mar 6 17:52:15 2014
@@ -0,0 +1,147 @@
+http://www.w3.org/TR/html4/loose.dtd";>
+
+
+
+
+ Apache Accumulo 1.5.1 Release Notes
+
+
+
+
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-21103458-6']);
+_gaq.push(['_setDomainName', 'apache.org']);
+_gaq.push(['_setAllowLinker', true]);
+_gaq.push(['_trackPageview']);
+
+(function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript';
ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? '<a rel="nofollow" href="https://ssl">https://ssl</a>' :
'<a rel="nofollow" href="http://www">http://www</a>') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+})();
+
+
+
+
+
+
+
+
+
+
+
+ Project
+
+Home
+Downloads
+Features
+http://www.apache.org/licenses/LICENSE-2.0";>License
+
+Community
+
+Get Involved
+Mailing Lists
+People
+
+Development
+
+Source & Guide
+Git WIP
+Contrib Projects
+Making Releases
+https://issues.apache.org/jira/browse/accumulo";>Issues
+https://builds.apache.org/view/A-D/view/Accumulo/";>Builds
+
+Documentation
+
+Manual 1.4 / 1.5
+Javadoc 1.4 / 1.5
+Examples 1.4 / 1.5
+Screenshots
+Papers & Other Links
+Glossary
+
+ASF links
+
+http://www.apache.org";>Apache Software Foundation
+http://www.apache.org/foundation/sponsorship.html";>Sponsorship
+http://www.apache.org/security/";>Security
+http://www.apache.org/foundation/thanks.html";>Thanks
+
+
+
+
+™
+
+
+
+Apache Accumulo 1.5.1 Release Notes
+Accumulo 1.5.1
Release Notes (Work in progress)
+Notable Improvements
+Accumulo client code creates background threads that users can not stop.
This
+causes problems when using Accumulo with Tomcat or JBoss. https://issues.apache.org/jira/browse/ACCUMULO-2128";>ACCUMULO-2128
+introduced the static utility org.apache.accumulo.core.util.CleanUp to clean
+these threads up.
+If IPv6 is enabled on nodes but not in use on the network, then Accumulo may
+have issues communicating with itself. https://issues.apache.org/jira/browse/ACCUMULO-2262";>ACCUMULO-2262
adds java
+configuration to startup scripts to prefer IPv4.
+https://issues.apache.org/jira/browse/ACCUMULO-1933";>ACCUMULO-1933
allows lower case memory units in Accumulo configuration.
+https://issues.apache.org/jira/browse/ACCUMULO-2360";>ACCUMULO-2360
allows users to configure the maximum frame size an
+Accumulo server will read. This prevents non Accumulo client from connecting
+and causing memory exhaustion.
+The following documentation updates were made : https://issues.apache.org/jira/browse/ACCUMULO-2127";>ACCUMULO-2127,
+https://issues.apache.org/jira/browse/ACCUMULO-1956";>ACCUMULO-1956,
and https://issues.apache.org/jira/browse/ACCUMULO-1428";>ACCUMULO-1428.
+Notable Bug Fixes
+
+https://issues.apache.org/jira/browse/ACCUMULO-1800";>ACCUMULO-1800
fixed deletes made via the Proxy.
+https://issues.apache.org/jira/browse/ACCUMULO-1994";>ACCUMULO-1994
fixed ranges in the Proxy.
+https://issues.apache.org/jira/browse/ACCUMULO-2234";>ACCUMULO-2234
fixed offline map reduce over non default HDFS location
+https://issues.apache.org/jira/browse/ACCUMULO-1615";>ACCUMULO-1615
fixed service accumulo-tserver stop
+https://issues.apache.org/jira/browse/ACCUMULO-1876";>ACCUMULO-1876
fixed issues with ivy
+
+Some important internal bugs were fixed in Accumulo that should be
considered
+when deciding to upgrade. These bugs are : https://issues.apache.org/jira/browse/ACCUMULO-2057";>ACCUMULO-2057,
+https://issues.apache.org/jira/browse/ACCUMULO-2261";>ACCUMULO-2261,
https://issues.apache.org/jira/browse/ACCUMUL
svn commit: r900335 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html release_notes/1.5.1.html release_notes/release_notes.html
Author: buildbot
Date: Thu Mar 6 20:37:49 2014
New Revision: 900335
Log:
Staging update by buildbot for accumulo
Added:
websites/staging/accumulo/trunk/content/release_notes/1.5.1.html
Removed:
websites/staging/accumulo/trunk/content/release_notes/release_notes.html
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/downloads/index.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 6 20:37:49 2014
@@ -1 +1 @@
-1574980
+1575035
Modified: websites/staging/accumulo/trunk/content/downloads/index.html
==
--- websites/staging/accumulo/trunk/content/downloads/index.html (original)
+++ websites/staging/accumulo/trunk/content/downloads/index.html Thu Mar 6
20:37:49 2014
@@ -92,7 +92,7 @@
Apache Accumulo Downloads
1.5.1 (latest)
-The most recent Apache Accumulo™ release is version 1.5.1. See the
https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=3478f71ae888f8d73aaa93837319a6dbb4ba0c8a";
title="1.5.1 CHANGES">CHANGES.
+The most recent Apache Accumulo™ release is version 1.5.1. See the
release notes and https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=3478f71ae888f8d73aaa93837319a6dbb4ba0c8a";
title="1.5.1 CHANGES">CHANGES.
Be sure to verify your downloads by these http://www.apache.org/info/verification.html";
title="Verify">procedures using these http://www.apache.org/dist/accumulo/KEYS"; title="KEYS">KEYS.
For convenience, http://www.apache.org/dist/accumulo/1.5.1/MD5SUM";>MD5 and http://www.apache.org/dist/accumulo/1.5.1/SHA1SUM";>SHA1 hashes are
also available.
Generic Binaries
Added: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html
==
--- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (added)
+++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Thu Mar 6
20:37:49 2014
@@ -0,0 +1,206 @@
+http://www.w3.org/TR/html4/loose.dtd";>
+
+
+
+
+ Apache Accumulo 1.5.1 Release Notes
+
+
+
+
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-21103458-6']);
+_gaq.push(['_setDomainName', 'apache.org']);
+_gaq.push(['_setAllowLinker', true]);
+_gaq.push(['_trackPageview']);
+
+(function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript';
ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? '<a rel="nofollow" href="https://ssl">https://ssl</a>' :
'<a rel="nofollow" href="http://www">http://www</a>') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+})();
+
+
+
+
+
+
+
+
+
+
+
+ Project
+
+Home
+Downloads
+Features
+http://www.apache.org/licenses/LICENSE-2.0";>License
+
+Community
+
+Get Involved
+Mailing Lists
+People
+
+Development
+
+Source & Guide
+Git WIP
+Contrib Projects
+Making Releases
+https://issues.apache.org/jira/browse/accumulo";>Issues
+https://builds.apache.org/view/A-D/view/Accumulo/";>Builds
+
+Documentation
+
+Manual 1.4 / 1.5
+Javadoc 1.4 / 1.5
+Examples 1.4 / 1.5
+Screenshots
+Papers & Other Links
+Glossary
+
+ASF links
+
+http://www.apache.org";>Apache Software Foundation
+http://www.apache.org/foundation/sponsorship.html";>Sponsorship
+http://www.apache.org/security/";>Security
+http://www.apache.org/foundation/thanks.html";>Thanks
+
+
+
+
+™
+
+
+
+Apache Accumulo 1.5.1 Release Notes
+Apache Accumulo 1.5.1 is a maintenance release on the 1.5 version
branch.
+This release is contains changes from over 200 issues, comprised of bug fixes
+(client side and server side), new test cases, updated Hadoop support, and
more.
+As this is a maintenance release, Apache Accumulo 1.5.1 has no client API
+incompatibilities over Apache Accumulo 1.5.0 and requires no manual upgrade
+process. Users of 1.5.0 are strongly encouraged to update as soon as possible
+to benefit from the improvements.
+Notable Improvements
+While new features are typically not added in a bug-fix release as 1.5.1,
the
+community does create a variety of improvements that are API compatible.
Contained
+here are some of the more notable improvements.
+PermGen Leak from Client API
+Accumulo's client code creates background threads that users presently
cannot
+sto
svn commit: r900351 - in /websites/staging/accumulo/trunk/content: ./ 1.5/accumulo_user_manual.pdf
Author: buildbot Date: Thu Mar 6 22:27:08 2014 New Revision: 900351 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/1.5/accumulo_user_manual.pdf Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 22:27:08 2014 @@ -1 +1 @@ -1575035 +1575077 Modified: websites/staging/accumulo/trunk/content/1.5/accumulo_user_manual.pdf == Binary files - no diff available.
svn commit: r900353 - in /websites/staging/accumulo/trunk/content: ./ 1.5/apidocs/ extpaths.txt
Author: buildbot Date: Thu Mar 6 22:51:18 2014 New Revision: 900353 Log: Staging update by buildbot for accumulo Removed: websites/staging/accumulo/trunk/content/1.5/apidocs/ Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/extpaths.txt Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 22:51:18 2014 @@ -1 +1 @@ -1575079 +1575084 Modified: websites/staging/accumulo/trunk/content/extpaths.txt == --- websites/staging/accumulo/trunk/content/extpaths.txt (original) +++ websites/staging/accumulo/trunk/content/extpaths.txt Thu Mar 6 22:51:18 2014 @@ -1 +1,2 @@ 1.4/apidocs +1.5/apidocs
svn commit: r900352 - in /websites/staging/accumulo/trunk/content: ./ 1.5/apidocs/ 1.5/apidocs/org/ 1.5/apidocs/org/apache/ 1.5/apidocs/org/apache/accumulo/ 1.5/apidocs/org/apache/accumulo/core/ 1.5/a
Author: buildbot Date: Thu Mar 6 22:48:06 2014 New Revision: 900352 Log: Staging update by buildbot for accumulo [This commit notification would consist of 1191 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.]
svn commit: r900355 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Thu Mar 6 23:06:54 2014 New Revision: 900355 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 23:06:54 2014 @@ -1 +1 @@ -1575084 +1575093 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Thu Mar 6 23:06:54 2014 @@ -92,7 +92,7 @@ Apache Accumulo 1.5.1 Release Notes Apache Accumulo 1.5.1 is a maintenance release on the 1.5 version branch. -This release is contains changes from over 200 issues, comprised of bug fixes +This release contains changes from over 200 issues, comprised of bug fixes (client side and server side), new test cases, updated Hadoop support, and more. As this is a maintenance release, Apache Accumulo 1.5.1 has no client API incompatibilities over Apache Accumulo 1.5.0 and requires no manual upgrade
svn commit: r900359 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Thu Mar 6 23:21:15 2014 New Revision: 900359 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 23:21:15 2014 @@ -1 +1 @@ -1575093 +1575094 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Thu Mar 6 23:21:15 2014 @@ -93,7 +93,8 @@ Apache Accumulo 1.5.1 Release Notes Apache Accumulo 1.5.1 is a maintenance release on the 1.5 version branch. This release contains changes from over 200 issues, comprised of bug fixes -(client side and server side), new test cases, updated Hadoop support, and more. +(client side and server side), new test cases, and updated Hadoop support +contributed by over 30 different contributors and committers. As this is a maintenance release, Apache Accumulo 1.5.1 has no client API incompatibilities over Apache Accumulo 1.5.0 and requires no manual upgrade process. Users of 1.5.0 are strongly encouraged to update as soon as possible @@ -123,6 +124,13 @@ Additionally, a non-intuitive error was Apache Thrift is used as the internal RPC service. https://issues.apache.org/jira/browse/ACCUMULO-2360";>ACCUMULO-2360 allows users to configure the maximum frame size an Accumulo server will read. This prevents non Accumulo client from connecting and causing memory exhaustion. +Hadoop Versions +Since Apache Accumulo 1.5.0 was released, Apache Hadoop 2.2.0 was also released +as the first generally available (GA) Hadoop 2 release. This was a very exciting release +for a number of reasons, but this also caused additional effort on Accumulo's part to +ensure that Apache Accumulo continues to work across multiple Hadoop versions. Apache Accumulo 1.5.1 +should function with any recent Hadoop 1 or Hadoop 2 without any special steps, tricks or instructions +required. Notable Bug Fixes As with any Apache Accumulo release, we have numerous bug fixes that have been fixed. Most are very subtle and won't affect the common user; however, some notable bugs were resolved
svn commit: r900361 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Thu Mar 6 23:32:49 2014 New Revision: 900361 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 6 23:32:49 2014 @@ -1 +1 @@ -1575094 +1575095 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Thu Mar 6 23:32:49 2014 @@ -124,13 +124,21 @@ Additionally, a non-intuitive error was Apache Thrift is used as the internal RPC service. https://issues.apache.org/jira/browse/ACCUMULO-2360";>ACCUMULO-2360 allows users to configure the maximum frame size an Accumulo server will read. This prevents non Accumulo client from connecting and causing memory exhaustion. +MultiTableBatchWriter concurrency +The MultiTableBatchWriter is a class which allows multiple tables to be written to +from a single object that maintains a single buffer for caching Mutations across all tables. This is desirable +as it greatly simplifies the JVM heap usage from caching Mutations across +many tables. Sadly, in Apache Accumulo 1.5.0, concurrent access to a single MultiTableBatchWriter +heavily suffered from synchronization issues. https://issues.apache.org/jira/browse/ACCUMULO-1833";>ACCUMULO-1833 introduces a fix +which alleviates the blocking and idle-wait that previously occurred when multiple threads accessed +a single MultiTableBatchWriter instance concurrently. Hadoop Versions Since Apache Accumulo 1.5.0 was released, Apache Hadoop 2.2.0 was also released as the first generally available (GA) Hadoop 2 release. This was a very exciting release for a number of reasons, but this also caused additional effort on Accumulo's part to ensure that Apache Accumulo continues to work across multiple Hadoop versions. Apache Accumulo 1.5.1 should function with any recent Hadoop 1 or Hadoop 2 without any special steps, tricks or instructions -required. +required. Notable Bug Fixes As with any Apache Accumulo release, we have numerous bug fixes that have been fixed. Most are very subtle and won't affect the common user; however, some notable bugs were resolved
svn commit: r900365 - in /websites/staging/accumulo/trunk/content: ./ 1.5/apidocs/ 1.5/apidocs/org/ 1.5/apidocs/org/apache/ 1.5/apidocs/org/apache/accumulo/ 1.5/apidocs/org/apache/accumulo/core/ 1.5/a
Author: buildbot Date: Fri Mar 7 00:22:20 2014 New Revision: 900365 Log: Staging update by buildbot for accumulo [This commit notification would consist of 1191 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.]
svn commit: r900368 - in /websites/staging/accumulo/trunk/content: ./ 1.5/apidocs/ extpaths.txt
Author: buildbot Date: Fri Mar 7 00:31:00 2014 New Revision: 900368 Log: Staging update by buildbot for accumulo Removed: websites/staging/accumulo/trunk/content/1.5/apidocs/ Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/extpaths.txt Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 7 00:31:00 2014 @@ -1 +1 @@ -1575103 +1575105 Modified: websites/staging/accumulo/trunk/content/extpaths.txt == --- websites/staging/accumulo/trunk/content/extpaths.txt (original) +++ websites/staging/accumulo/trunk/content/extpaths.txt Fri Mar 7 00:31:00 2014 @@ -1 +1,2 @@ 1.4/apidocs +1.5/apidocs
svn commit: r900469 - in /websites/staging/accumulo/trunk/content: ./ doap_Accumulo.rdf
Author: buildbot Date: Fri Mar 7 16:43:13 2014 New Revision: 900469 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/doap_Accumulo.rdf Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 7 16:43:13 2014 @@ -1 +1 @@ -1575105 +1575316 Modified: websites/staging/accumulo/trunk/content/doap_Accumulo.rdf == Binary files - no diff available.
svn commit: r900471 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Author: buildbot Date: Fri Mar 7 17:05:47 2014 New Revision: 900471 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 7 17:05:47 2014 @@ -1 +1 @@ -1575316 +1575325 Modified: websites/staging/accumulo/trunk/content/releasing.html == --- websites/staging/accumulo/trunk/content/releasing.html (original) +++ websites/staging/accumulo/trunk/content/releasing.html Fri Mar 7 17:05:47 2014 @@ -155,9 +155,27 @@ out to all of the mirrors. Update the Website After a successful vote, this website needs to be updated with the new artifacts. The downloads page should be updated with the new information. A new minor release should replace the previous minor release in the major -version. The Javadocs should be updated, with special care being taken to ensure that Javadocs are http://www.kb.cert.org/vuls/id/225657";>patched before +version. The user manual should also be updated if changes were made to it. +Javadocs +Javadocs are a little convoluted to update. First off, be sure that the javadocs are http://www.kb.cert.org/vuls/id/225657";>patched before uploading as long as Java 6 is the version targeted by Accumulo (with greater than Java 7u21 being used once we -switch to Java 7). The user manual should also be updated if changes were made to it. +switch to Java 7). Despite the javadocs not appearing in the CMS SVN repository, this is +where they need to be committed using http://www.apache.org/dev/cmsref#extpaths";>extpaths. You can follow the steps below to update +the javadocs. + +Extract javadocs from binary tarball from the release +Run the vulnerability-check tool +Checkout the https://svn.apache.org/repos/asf/accumulo/site/trunk";>Accumulo CMS repository +Copy the entire apidocs folder in the appropriate version folder in the CMS repository (e.g. content/1.5/apidocs for a 1.5 release) +Remove the appropriate entry from content/extpaths.txt (e.g. 1.5/apidocs for 1.5 release) +Commit the changes +Wait for the staging build to complete, and then publish the changes to the production site. +Remove the apidocs folder you created from the CMS repository (e.g. content/1.5/apidocs) +Re-add the entry in extpaths.txt that you previously removed. +Commit the changes +Wait for the staging build to complete, and then publish the changes to the production site again. +Verify that javadocs have been updated on the production site + References Some good references that explain a few things:
svn commit: r901295 - in /websites/staging/accumulo/trunk/content: ./ source.html
Author: buildbot Date: Wed Mar 12 17:30:56 2014 New Revision: 901295 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/source.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 12 17:30:56 2014 @@ -1 +1 @@ -1575325 +1576829 Modified: websites/staging/accumulo/trunk/content/source.html == --- websites/staging/accumulo/trunk/content/source.html (original) +++ websites/staging/accumulo/trunk/content/source.html Wed Mar 12 17:30:56 2014 @@ -139,6 +139,17 @@ need to install or modify the Thrift def Accumulo https://issues.apache.org/jira/browse/accumulo";>tracks issues with http://www.atlassian.com/software/jira/overview";>JIRA. Every commit should reference a JIRA ticket of the form ACCUMULO-#. Merging Practices Changes should be merged from earlier branches of Accumulo to later branches. Ask the dev list for instructions. +Public API +The following classes constitute the Accumulo "public API": + +All classes in org.apache.accumulo.core.client except those in "impl" subpackages +The following classes in org.apache.accumulo.core.data: +Key +Mutation +Value +Range + +Changes to non-private members of those classes are subject to additional scrutiny to minimize compatibility problems across Accumulo versions. Coding Practices License Header: Always add the current ASF license header as described in http://www.apache.org/legal/src-headers.html";>ASF Source Header.
svn commit: r901296 - in /websites/staging/accumulo/trunk/content: ./ source.html
Author: buildbot Date: Wed Mar 12 17:33:05 2014 New Revision: 901296 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/source.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 12 17:33:05 2014 @@ -1 +1 @@ -1576829 +1576830 Modified: websites/staging/accumulo/trunk/content/source.html == --- websites/staging/accumulo/trunk/content/source.html (original) +++ websites/staging/accumulo/trunk/content/source.html Wed Mar 12 17:33:05 2014 @@ -143,11 +143,7 @@ need to install or modify the Thrift def The following classes constitute the Accumulo "public API": All classes in org.apache.accumulo.core.client except those in "impl" subpackages -The following classes in org.apache.accumulo.core.data: -Key -Mutation -Value -Range +The following classes in org.apache.accumulo.core.data: Key, Mutation, Value, Range Changes to non-private members of those classes are subject to additional scrutiny to minimize compatibility problems across Accumulo versions. Coding Practices
svn commit: r901298 - in /websites/staging/accumulo/trunk/content: ./ css/accumulo.css
Author: buildbot
Date: Wed Mar 12 17:35:43 2014
New Revision: 901298
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/css/accumulo.css
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 12 17:35:43 2014
@@ -1 +1 @@
-1576830
+1576831
Modified: websites/staging/accumulo/trunk/content/css/accumulo.css
==
--- websites/staging/accumulo/trunk/content/css/accumulo.css (original)
+++ websites/staging/accumulo/trunk/content/css/accumulo.css Wed Mar 12
17:35:43 2014
@@ -69,7 +69,12 @@ h1, h2, h3, h4, h5, h6 {
font-size: 1.2em;
margin-top: 2em;
}
-#content h3, h4, h5, h6 {
+#content h3 {
+border-bottom: medium none;
+font-size: 1.1em;
+margin-bottom: 0;
+}
+#content h4, h5, h6 {
border-bottom: medium none;
font-size: 1em;
margin-bottom: 0;
svn commit: r901493 - in /websites/staging/accumulo/trunk/content: ./ source.html
Author: buildbot Date: Thu Mar 13 23:28:36 2014 New Revision: 901493 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/source.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 13 23:28:36 2014 @@ -1 +1 @@ -1577378 +1577379 Modified: websites/staging/accumulo/trunk/content/source.html == --- websites/staging/accumulo/trunk/content/source.html (original) +++ websites/staging/accumulo/trunk/content/source.html Thu Mar 13 23:28:36 2014 @@ -140,7 +140,7 @@ need to install or modify the Thrift def Merging Practices Changes should be merged from earlier branches of Accumulo to later branches. Ask the dev list for instructions. Public API -Refer to the README in the release you are using to see what packages in the public API. +Refer to the README in the release you are using to see what packages are in the public API. Changes to non-private members of those classes are subject to additional scrutiny to minimize compatibility problems across Accumulo versions. Coding Practices
svn commit: r901492 - in /websites/staging/accumulo/trunk/content: ./ source.html
Author: buildbot Date: Thu Mar 13 23:27:53 2014 New Revision: 901492 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/source.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 13 23:27:53 2014 @@ -1 +1 @@ -1576831 +1577378 Modified: websites/staging/accumulo/trunk/content/source.html == --- websites/staging/accumulo/trunk/content/source.html (original) +++ websites/staging/accumulo/trunk/content/source.html Thu Mar 13 23:27:53 2014 @@ -140,11 +140,7 @@ need to install or modify the Thrift def Merging Practices Changes should be merged from earlier branches of Accumulo to later branches. Ask the dev list for instructions. Public API -The following classes constitute the Accumulo "public API": - -All classes in org.apache.accumulo.core.client except those in "impl" subpackages -The following classes in org.apache.accumulo.core.data: Key, Mutation, Value, Range - +Refer to the README in the release you are using to see what packages in the public API. Changes to non-private members of those classes are subject to additional scrutiny to minimize compatibility problems across Accumulo versions. Coding Practices
svn commit: r901581 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Fri Mar 14 16:52:51 2014 New Revision: 901581 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 14 16:52:51 2014 @@ -1 +1 @@ -1577610 +1577611 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Fri Mar 14 16:52:51 2014 @@ -213,7 +213,7 @@ column mean that all required release te Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run on a number of nodes. Agitation refers to randomly killing Accumulo processes, Hadoop Datanode processes, and, in HDFS High-Availability instances, forcing NameNode failover. - + OS Hadoop
svn commit: r901580 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Fri Mar 14 16:50:26 2014 New Revision: 901580 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 14 16:50:26 2014 @@ -1 +1 @@ -1577379 +1577610 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Fri Mar 14 16:50:26 2014 @@ -200,6 +200,61 @@ mutation queues. https://issues.apache.org/jira/browse/ACCUMULO-2226";>ACCUMULO-2226 https://issues.apache.org/jira/browse/ACCUMULO-1470";>ACCUMULO-1470 +Testing +Below is a list of all platforms that 1.5.1 was tested against by developers. A value of All in the "Tests" +column mean that all required release tests were run on this platform. That list includes the following: + +Successfully run all unit tests +Successfully run all functional test (test/system/auto) +Successfully complete two 24-hour RandomWalk tests (LongClean module), with and without "agitation" +Successfully complete two 24-hour Continuous Ingest tests, with and without "agitation", with data verification +Successfully complete two 72-hour Continuous Ingest tests, with and without "agitation" + +Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run +on a number of nodes. Agitation refers to randomly killing Accumulo processes, Hadoop Datanode processes, +and, in HDFS High-Availability instances, forcing NameNode failover. + + +OS +Hadoop +Nodes +ZooKeeper +HDFS High-Availability +Tests + + +CentOS 6.5 +HDP 2.0 (Apache 2.2.0) +6 +HDP 2.0 (Apache 3.4.5) +Yes (QJM) +All required tests + + +CentOS 6.4 +CDH 4.5.0 (2.0.0+cdh4.5.0) +7 +CDH 4.5.0 (3.4.5+cdh4.5.0) +Yes (QJM) +Unit, functional and 24hr Randomwalk w/ agitation + + +CentOS 6.4 +CDH 4.5.0 (2.0.0+cdh4.5.0) +7 +CDH 4.5.0 (3.4.5+cdh4.5.0) +Yes (QJM) +2x 24/hr continuous ingest w/ verification + + +CentOS 6.3 +Apache 1.0.4 +1 +Apache 3.3.5 +No +Sniff test, unit and functional tests + +
svn commit: r901582 - in /websites/staging/accumulo/trunk/content: ./ css/accumulo.css
Author: buildbot
Date: Fri Mar 14 17:00:12 2014
New Revision: 901582
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/css/accumulo.css
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar 14 17:00:12 2014
@@ -1 +1 @@
-1577611
+1577612
Modified: websites/staging/accumulo/trunk/content/css/accumulo.css
==
--- websites/staging/accumulo/trunk/content/css/accumulo.css (original)
+++ websites/staging/accumulo/trunk/content/css/accumulo.css Fri Mar 14
17:00:12 2014
@@ -159,3 +159,15 @@ dt {
display: inline;
float: left;
}
+
+#release_notes_testing {
+border-collapse:collapse;
+}
+
+#release_notes_testing, #release_notes_testing tbody tr,
#release_notes_testing tbody tr th, #release_notes_testing tbody tr td {
+border: 2px solid black;
+}
+
+#release_notes_testing tbody tr th, #release_notes_testing tbody tr td {
+padding: 5px;
+}
\ No newline at end of file
svn commit: r901590 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Fri Mar 14 17:59:36 2014 New Revision: 901590 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 14 17:59:36 2014 @@ -1 +1 @@ -1577612 +1577625 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Fri Mar 14 17:59:36 2014 @@ -252,7 +252,7 @@ and, in HDFS High-Availability instances 1 Apache 3.3.5 No -Sniff test, unit and functional tests +Local testing, unit and functional tests
svn commit: r901594 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Fri Mar 14 18:11:04 2014 New Revision: 901594 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 14 18:11:04 2014 @@ -1 +1 @@ -1577625 +1577644 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Fri Mar 14 18:11:04 2014 @@ -254,6 +254,14 @@ and, in HDFS High-Availability instances No Local testing, unit and functional tests + +RHEL 6.4 +Apache 2.2.0 +10 +Apache 3.4.5 +No +Functional tests +
svn commit: r901595 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.1.html
Author: buildbot Date: Fri Mar 14 18:14:09 2014 New Revision: 901595 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 14 18:14:09 2014 @@ -1 +1 @@ -1577644 +1577646 Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.5.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.5.1.html Fri Mar 14 18:14:09 2014 @@ -201,8 +201,8 @@ mutation queues. https://issues.apache.org/jira/browse/ACCUMULO-1470";>ACCUMULO-1470 Testing -Below is a list of all platforms that 1.5.1 was tested against by developers. A value of All in the "Tests" -column mean that all required release tests were run on this platform. That list includes the following: +Below is a list of all platforms that 1.5.1 was tested against by developers. Each Apache Accumulo release +has a set of tests that must be run before the candidate is capable of becoming an official release. That list includes the following: Successfully run all unit tests Successfully run all functional test (test/system/auto) @@ -211,7 +211,7 @@ column mean that all required release te Successfully complete two 72-hour Continuous Ingest tests, with and without "agitation" Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run -on a number of nodes. Agitation refers to randomly killing Accumulo processes, Hadoop Datanode processes, +on any number of nodes. Agitation refers to randomly restarting Accumulo processes and Hadoop Datanode processes, and, in HDFS High-Availability instances, forcing NameNode failover.
svn commit: r901656 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Sat Mar 15 04:10:54 2014
New Revision: 901656
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Sat Mar 15 04:10:54 2014
@@ -1 +1 @@
-1577646
+158
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Sat Mar 15 04:10:54 2014
@@ -157,6 +157,7 @@ tr:nth-child(2n+1) {
etcolemanEd ColemanET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Ed Kohlweyhttp://www.boozallen.com/>Booz
Allen Hamilton
edwardyoonEdward Yoon
+ Hung Phamhttp://www.cloudera.com/";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
jaredwinickJared Winickhttp://www.koverse.com";>KoverseMT (http://www.timeanddate.com/library/abbreviations/timezones/na/mst.html>-7
/ http://www.timeanddate.com/library/abbreviations/timezones/na/mdt.html>-6)
Jason Then
Jay Shipper
svn commit: r902049 [3/3] - in /websites/staging/accumulo/trunk/content: ./ 1.4/ 1.4/examples/ 1.4/user_manual/ 1.5/ 1.5/examples/
Modified: websites/staging/accumulo/trunk/content/1.5/examples/filedata.html == --- websites/staging/accumulo/trunk/content/1.5/examples/filedata.html (original) +++ websites/staging/accumulo/trunk/content/1.5/examples/filedata.html Mon Mar 17 21:10:31 2014 @@ -98,8 +98,8 @@ The example has the following classes:ChunkCombiner - An Iterator that dedupes file data and sets their visibilities to a combined visibility based on current references to the file data. ChunkInputFormat - An Accumulo InputFormat that provides keys containing file info (List>) and values with an InputStream over the file (ChunkInputStream). ChunkInputStream - An input stream over file data stored in Accumulo. -FileDataIngest - Takes a list of files and archives them into Accumulo keyed on the SHA1 hashes of the files. -FileDataQuery - Retrieves file data based on the SHA1 hash of the file. (Used by the dirlist.Viewer.) +FileDataIngest - Takes a list of files and archives them into Accumulo keyed on hashes of the files. +FileDataQuery - Retrieves file data based on the hash of the file. (Used by the dirlist.Viewer.) KeyUtil - A utility for creating and parsing null-byte separated strings into/from Text objects. VisibilityCombiner - A utility for merging visibilities into the form (VIS1)|(VIS2)|...
svn commit: r902272 - in /websites/staging/accumulo/trunk/content: ./ 1.5/examples/index.html
Author: buildbot Date: Wed Mar 19 03:05:37 2014 New Revision: 902272 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/1.5/examples/index.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 19 03:05:37 2014 @@ -1 +1 @@ -1578577 +1579115 Modified: websites/staging/accumulo/trunk/content/1.5/examples/index.html == --- websites/staging/accumulo/trunk/content/1.5/examples/index.html (original) +++ websites/staging/accumulo/trunk/content/1.5/examples/index.html Wed Mar 19 03:05:37 2014 @@ -100,7 +100,7 @@ to as "zookeepers". -Create an Accumulo user (see the user manual), or use the root user. +Create an Accumulo user (see the user manual), or use the root user. The "username" Accumulo user name with password "password" is used throughout the examples. This user needs the ability to create tables.
svn commit: r902356 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot
Date: Wed Mar 19 17:16:22 2014
New Revision: 902356
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/bylaws.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 19 17:16:22 2014
@@ -1 +1 @@
-1579297
+1579300
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 17:16:22 2014
@@ -180,11 +180,16 @@ stability, and robustness of both code a
Min. Length (days)
Code Change
A change made to a codebase of the project. This includes source code,
documentation, website content, etc.
-Lazy approval, moving to consensus approval if a -1 is received.
+Lazy approval, moving to consensus approval upon veto
Active committers
1
Release Plan
Defines the timetable and actions for a release. The plan also
nominates a Release Manager.
+Lazy approval, moving to majority approval upon veto
+Active committers
+3
+Release Plan Cancellation
+Cancels an active release plan, due to a need to re-plan (e.g.,
discovery of a major issue).
Majority approval
Active committers
3
@@ -214,6 +219,10 @@ stability, and robustness of both code a
Active PMC members
7
+
+No other voting actions are defined. If a new one is found to be needed, it
should be added to these bylaws.
+For the purposes of the "Adoption of New Codebase" action, the Accumulo
codebase is defined as the Accumulo site content, primary project code, and all
contributed code ("contribs") as they exist in their respective repositories.
Adoption of a new codebase generally refers to the creation of a new contrib
repository, but could cover, for example, a rework of the project site, or
merging a contrib project into the primary codebase.
+Voting actions for the removal of a committer or PMC member are
intentionally not defined. According to ASF rules, http://www.apache.org/dev/committers.html#committer-set-term";>committer
status never expires and http://www.apache.org/dev/pmc.html#pmc-removal";>the ASF board removes PMC
members.
svn commit: r902360 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Wed Mar 19 17:34:27 2014 New Revision: 902360 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 19 17:34:27 2014 @@ -1 +1 @@ -1579300 +1579304 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 17:34:27 2014 @@ -135,6 +135,17 @@ stability, and robustness of both code a A PMC member is considered emeritus, meaning inactive, by his or her own declaration or by not contributing in any form to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update his/her status on the web page accordingly. The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (Vice President, Apache Accumulo) and has primary responsibility to the board for the management of the projects within the scope of the Accumulo PMC. The chair reports to the board quarterly on developments within the Accumulo project. When the current chair of the PMC resigns, the PMC votes to recommend a new chair using consensus approval, but the decision must be ratified by the Apache board. +Release Manager +The https://www.apache.org/dev/release-publishing.html";>ASF release process defines the https://www.apache.org/dev/release-publishing.html#release_manager";>release manager as an individual responsible for shepherding a new project release. Any committer may serve as a release manager. The release manager for a release is chosen as part of the release plan. +At a minimum, a release manager is responsible for packaging a release candidate for a vote and signing and publishing an approved release candidate. An Accumulo release manager is also expected to: + +guide whether changes after feature freeze or code freeze should be included in the release +ensure that required release testing is being conducted +track whether the release is on target for its expected release date +determine if a re-plan may be needed and, if so, call a vote +call votes on release candidates + +http://accumulo.apache.org/releasing.html";>Release guidelines and http://accumulo.apache.org/releasing.html";>details on the mechanics of creating an Accumulo release are available on the Accumulo project site. Decision Making Within the Accumulo project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'consensus approval'. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval. Voting @@ -184,7 +195,7 @@ stability, and robustness of both code a Active committers 1 Release Plan -Defines the timetable and actions for a release. The plan also nominates a Release Manager. +Defines the timetable and actions for an upcoming release. The plan also nominates a Release Manager. Lazy approval, moving to majority approval upon veto Active committers 3 @@ -194,7 +205,7 @@ stability, and robustness of both code a Active committers 3 Product Release -When a release of one of the project's products is ready, a vote is required to accept the release as an official release of the project. +Accepts or rejects a release candidate as an official release of the project. Majority approval Active PMC members 3
svn commit: r902354 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Wed Mar 19 16:59:34 2014 New Revision: 902354 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 19 16:59:34 2014 @@ -1 +1 @@ -1579115 +1579297 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 16:59:34 2014 @@ -110,14 +110,14 @@ All Apache committers are required to have a signed http://www.apache.org/licenses/icla.txt";>Contributor License Agreement (CLA) on file with the Apache Software Foundation. Under the terms of the CLA that all committers must sign, a committer's primary responsibility is to ensure that all code committed to Apache Accumulo is licensed appropriately and meets those criteria set forth in the CLA (including both original works and patches committed on behalf of other contributors). There is a http://www.apache.org/dev/committers.html";>Committer FAQ which provides more details on the requirements for committers. It is the custom of the Accumulo project to also invite each committer to become a member of the Accumulo PMC. Project Management Committee -The role of the PMC from a Foundation perspective is http://apache.org/foundation/how-it-works.html#pmc";>oversight. The main -role of the PMC is not code and not coding - but to ensure that all legal +The role of the PMC, from a Foundation perspective, is http://apache.org/foundation/how-it-works.html#pmc";>oversight. The main +role of the PMC is not code and not coding, but to ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole. That is key to our litigation protection mechanisms. -Secondly the role of the PMC is to further the long term development and +Secondly, the role of the PMC is to further the long-term development and health of the community as a whole, and to ensure that balanced and wide -scale peer review and collaboration does happen. Within the ASF we worry +scale peer review and collaboration does happen. Within the ASF, we worry about any community which centers around a few individuals who are working virtually uncontested. We believe that this is detrimental to quality, stability, and robustness of both code and long term social structures. @@ -162,13 +162,13 @@ stability, and robustness of both code a Consensus Approval A consensus approval vote passes with 3 binding +1 votes and no binding vetoes. Majority Approval -A majority approval vote passes with 3 binding +1 votes and more binding +1 votes that -1 votes. +A majority approval vote passes with 3 binding +1 votes and more binding +1 votes than -1 votes. Lazy Approval (or Lazy Consensus) An action with lazy approval is implicitly allowed unless a -1 vote is received, at which time, depending on the type of action, either majority approval or consensus approval must be obtained. Vetoes -A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid. +A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto, but merely that the veto is valid. If you disagree with a valid veto, you must lobby the person casting the veto to withdraw his or her veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in a timely manner. Actions This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in days. In general votes should not be called at times when it is known that interested members of the project will be unavailable.
svn commit: r902363 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot
Date: Wed Mar 19 17:43:40 2014
New Revision: 902363
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/bylaws.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 19 17:43:40 2014
@@ -1 +1 @@
-1579304
+1579315
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 17:43:40 2014
@@ -142,6 +142,7 @@ stability, and robustness of both code a
guide whether changes after feature freeze or code freeze should be
included in the release
ensure that required release testing is being conducted
track whether the release is on target for its expected release date
+adjust release plan dates to reflect the latest estimates
determine if a re-plan may be needed and, if so, call a vote
call votes on release candidates
@@ -234,6 +235,18 @@ stability, and robustness of both code a
No other voting actions are defined. If a new one is found to be needed, it
should be added to these bylaws.
For the purposes of the "Adoption of New Codebase" action, the Accumulo
codebase is defined as the Accumulo site content, primary project code, and all
contributed code ("contribs") as they exist in their respective repositories.
Adoption of a new codebase generally refers to the creation of a new contrib
repository, but could cover, for example, a rework of the project site, or
merging a contrib project into the primary codebase.
Voting actions for the removal of a committer or PMC member are
intentionally not defined. According to ASF rules, http://www.apache.org/dev/committers.html#committer-set-term";>committer
status never expires and http://www.apache.org/dev/pmc.html#pmc-removal";>the ASF board removes PMC
members.
+Release Plans
+The approval of a release plan begins the process of creating a new project
release. The process ends when a release candidate is approved.
+An Accumulo release plan consists of at least the following:
+
+a version number
+a feature freeze date
+a code freeze date
+a release date
+the choice of a release manager
+
+After feature freeze, new features should not be accepted for the release.
After code freeze, only critical fixes should be accepted for the release. The
release manager guides the decision on accepting changes.
+All dates in a plan are estimates, as unforeseen issues may require delays.
The release manager may adjust dates as needed. In serious circumstances, the
release manager may opt to call a re-plan vote.
svn commit: r902567 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Thu Mar 20 18:07:15 2014 New Revision: 902567 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 18:07:15 2014 @@ -1 +1 @@ -1579315 +1579698 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Thu Mar 20 18:07:15 2014 @@ -215,12 +215,12 @@ stability, and robustness of both code a Consensus approval Active PMC members 7 -New Committer or Reinstatement +New Committer When a new committer is proposed for the project. Consensus approval Active PMC members 3 -New PMC Member or Reinstatement +New PMC Member When a committer is proposed for the PMC. Consensus approval Active PMC members
svn commit: r902575 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Thu Mar 20 19:20:27 2014 New Revision: 902575 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 19:20:27 2014 @@ -1 +1 @@ -1579698 +1579718
svn commit: r902577 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Thu Mar 20 19:25:56 2014 New Revision: 902577 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 19:25:56 2014 @@ -1 +1 @@ -1579718 +1579720
svn commit: r902579 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Thu Mar 20 19:40:11 2014 New Revision: 902579 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 19:40:11 2014 @@ -1 +1 @@ -1579720 +1579722 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Thu Mar 20 19:40:11 2014 @@ -104,8 +104,8 @@ Contributors All of the volunteers who are contributing time, code, documentation, or resources to the Accumulo project are considered contributors. A contributor that makes sustained, welcome contributions to the project may be invited to become a committer, though the exact timing of such invitations depends on many factors. Committers -The project's committers are responsible for the project's technical management. Committers have write access to the project's code repositories and may cast binding votes on any technical discussion regarding Accumulo. Committer access is by invitation only and must be approved by consensus approval of the active PMC members. Upon acceptance of the invitation to become a committer, it is the accepting memberâs responsibility to update his/her status on the Accumulo web page accordingly. -A committer is considered emeritus, meaning inactive, by his or her own declaration or by not reviewing patches or committing patches to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update his/her status on the web page accordingly. +The project's committers are responsible for the project's technical management. Committers have write access to the project's code repositories and may cast binding votes on any technical discussion regarding Accumulo. Committer access is by invitation only and must be approved by consensus approval of the active PMC members. Upon acceptance of the invitation to become a committer, it is the accepting memberâs responsibility to update their status on the Accumulo web page accordingly. +A committer is considered emeritus, meaning inactive, by their own declaration or by not reviewing patches or committing patches to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update their status on the web page accordingly. An emeritus committerâs commit access may be disabled as part of routine security. Access shall not be removed without notifying the committer, and access shall be maintained if the committer wishes to leave it active. A committerâs commit access shall be reactivated upon the committerâs request to the PMC. All Apache committers are required to have a signed http://www.apache.org/licenses/icla.txt";>Contributor License Agreement (CLA) on file with the Apache Software Foundation. Under the terms of the CLA that all committers must sign, a committer's primary responsibility is to ensure that all code committed to Apache Accumulo is licensed appropriately and meets those criteria set forth in the CLA (including both original works and patches committed on behalf of other contributors). There is a http://www.apache.org/dev/committers.html";>Committer FAQ which provides more details on the requirements for committers. It is the custom of the Accumulo project to also invite each committer to become a member of the Accumulo PMC. @@ -131,8 +131,8 @@ stability, and robustness of both code a Maintaining these bylaws and other guidelines of the project. In particular, PMC members must understand both our project's criteria and ASF criteria for voting on a http://www.apache.org/dev/release.html#management";>release. -Membership of the PMC is by invitation only and must be approved by a consensus approval of active PMC members. Upon acceptance of the invitation to become a PMC member, it is the accepting memberâs respons
svn commit: r902586 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Thu Mar 20 20:29:26 2014 New Revision: 902586 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 20:29:26 2014 @@ -1 +1 @@ -1579722 +1579730
svn commit: r902587 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Thu Mar 20 20:34:15 2014 New Revision: 902587 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 20 20:34:15 2014 @@ -1 +1 @@ -1579730 +1579731
svn commit: r902642 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Fri Mar 21 02:42:17 2014 New Revision: 902642 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 21 02:42:17 2014 @@ -1 +1 @@ -1579731 +1579871 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Fri Mar 21 02:42:17 2014 @@ -200,8 +200,8 @@ Jira issue ACCUMULO-12345 that affects 1 For the given issue you intend to work on, choose the 'lowest' fixVersion - and create a branch for yourself to work in. -git checkout -b ACCUMULO-12345-my-work origin/1.5.1-SNAPSHOT + and create a branch for yourself to work in. This example is against fixVersion 1.5.2. +git checkout -b ACCUMULO-12345-my-work origin/1.5.2-SNAPSHOT Make commits as you see fit as you fix the issue, referencing the issue name @@ -211,13 +211,13 @@ Jira issue ACCUMULO-12345 that affects 1 Assuming others are developing against the version you also are, as you work, or before you create your patch, rebase your branch against the remote - to lift your changes to the top of your branch. -git pull --rebase origin 1.5.1-SNAPSHOT + to lift your changes to the top of your branch. The branch specified here should be the same one you used in step 4. +git pull --rebase origin 1.5.2-SNAPSHOT At this point, you can create a patch file from the upstream branch to - attach to the ACCUMULO-12345 Jira issue. -git format-patch 1.5.1-SNAPSHOT --stdout > ACCUMULO-12345.patch + attach to the ACCUMULO-12345 Jira issue. The branch specified here should be teh same one you used in step 4. +git format-patch --stdout origin/1.5.2-SNAPSHOT > ACCUMULO-12345.patch An alternative to creating a patch is submitting a request to pull your changes
svn commit: r902652 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Fri Mar 21 05:03:26 2014
New Revision: 902652
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar 21 05:03:26 2014
@@ -1 +1 @@
-1579871
+1579887
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Fri Mar 21 05:03:26 2014
@@ -146,6 +146,7 @@ tr:nth-child(2n+1) {
usernamenameorganizationtimezone
Aaron Glahehttp://www.data-tactics.com/>Data TaticsET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ Al KrinkerET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Alex Moundalexishttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Arshak Navruzyanhttp://www.argyledata.com/";>Argyle Data
Chris Bennight
svn commit: r902707 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Fri Mar 21 15:22:57 2014 New Revision: 902707 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 21 15:22:57 2014 @@ -1 +1 @@ -1579887 +1579957 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Fri Mar 21 15:22:57 2014 @@ -179,7 +179,7 @@ explanation is clear. The implementation Contributors -Use the following steps, original derived from Apache Kafka's https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow#GitWorkflow-Simplecontributorworkflow";>simple +Use the following steps, original derived from Apache Kafka's https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review";>simple contributor workflow. To be specific, let's consider a contributor wanting to work on a fix for the
svn commit: r902708 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Fri Mar 21 15:26:08 2014 New Revision: 902708 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 21 15:26:08 2014 @@ -1 +1 @@ -1579957 +1579959 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Fri Mar 21 15:26:08 2014 @@ -179,7 +179,7 @@ explanation is clear. The implementation Contributors -Use the following steps, original derived from Apache Kafka's https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review";>simple +Use the following steps, original derived from Apache Kafka's https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-Simplecontributorworkflow";>simple contributor workflow. To be specific, let's consider a contributor wanting to work on a fix for the
svn commit: r903472 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Author: buildbot Date: Tue Mar 25 07:29:21 2014 New Revision: 903472 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/governance/releasing.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 07:29:21 2014 @@ -1 +1 @@ -1579959 +1581267 Modified: websites/staging/accumulo/trunk/content/governance/releasing.html == --- websites/staging/accumulo/trunk/content/governance/releasing.html (original) +++ websites/staging/accumulo/trunk/content/governance/releasing.html Tue Mar 25 07:29:21 2014 @@ -140,21 +140,21 @@ Cluster based -The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node in psuedo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base will be exercised. For the purposes of release testing, you should note the number of nodes and versions used. See the Releasing section for more details. +The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node in pseudo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base will be exercised. For the purposes of release testing, you should note the number of nodes and versions used. See the Releasing section for more details. For versions prior to 1.6, all functional tests must complete successfully. See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests. -Two 24-hour periods of the randomwalk LongClean test with and without agitation need to be run successfully. +Two 24-hour periods of the LongClean module of the RandomWalk test need to be run successfully. One of them must use agitation and the other should not. See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean module. -Two 24-hour periods of continuous ingest with and without agitation need to be validated successfully. -See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying the continous ingest test. +Two 24-hour periods of the continuous ingest test must be validated successfully. One test period must use agitation and the other should not. +See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying the continuous ingest test. -Two 72-hour periods of continuous ingest with and without agitation. No validation is necessary but the cluster should be checked to ensure it is still functional. +Two 72-hour periods of continuous ingest must run. One test period must use agitation and the other should not. No validation is necessary but the cluster should be checked to ensure it is still functional. Releasing
svn commit: r903507 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Tue Mar 25 13:50:09 2014 New Revision: 903507 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 13:50:09 2014 @@ -1 +1 @@ -1581267 +1581322 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Tue Mar 25 13:50:09 2014 @@ -167,7 +167,7 @@ stability, and robustness of both code a All participants in the Accumulo project are encouraged to vote. For technical decisions, only the votes of active committers are binding. Non-binding votes are still useful for those with binding votes to understand the perception of an action across the wider Accumulo community. For PMC decisions, only the votes of active PMC members are binding. Voting can also be applied to changes to the Accumulo codebase. Please refer to the Accumulo commit and review standard for details. Approvals -There are the types of approvals that can be sought. Different actions require different types of approvals. +These are the types of approvals that can be sought. Different actions require different types of approvals. Approval Type Definition @@ -183,7 +183,7 @@ stability, and robustness of both code a A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto, but merely that the veto is valid. If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in a timely manner. Actions -This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in days. In general votes should not be called at times when it is known that interested members of the project will be unavailable. +This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in days. In general, votes should not be called at times when it is known that interested members of the project will be unavailable. Action Description @@ -225,6 +225,11 @@ stability, and robustness of both code a Consensus approval Active PMC members 3 +New PMC Chair +When a new PMC chair is chosen to succeed an outgoing chair. +Consensus approval +Active PMC members +3 Modifying Bylaws Modifying this document. Majority approval
svn commit: r903533 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot
Date: Tue Mar 25 15:45:47 2014
New Revision: 903533
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/bylaws.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 25 15:45:47 2014
@@ -1 +1 @@
-1581322
+1581380
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Tue Mar 25 15:45:47 2014
@@ -237,7 +237,7 @@ stability, and robustness of both code a
7
-No other voting actions are defined. If a new one is found to be needed, it
should be added to these bylaws.
+No other voting actions are defined; all other actions should presume Lazy
Approval (defaulting to Consensus Approval upon veto). If an action is voted on
multiple times, or if a different approval type is desired, these bylaws should
be amended to include the action.
For the purposes of the "Adoption of New Codebase" action, the Accumulo
codebase is defined as the Accumulo site content, primary project code, and all
contributed code ("contribs") as they exist in their respective repositories.
Adoption of a new codebase generally refers to the creation of a new contrib
repository, but could cover, for example, a rework of the project site, or
merging a contrib project into the primary codebase.
Voting actions for the removal of a committer or PMC member are
intentionally not defined. According to ASF rules, http://www.apache.org/dev/committers.html#committer-set-term";>committer
status never expires and http://www.apache.org/dev/pmc.html#pmc-removal";>the ASF board removes PMC
members.
Release Plans
svn commit: r903536 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Tue Mar 25 16:24:58 2014
New Revision: 903536
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 25 16:24:58 2014
@@ -1 +1 @@
-1581380
+1581405
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Tue Mar 25 16:24:58 2014
@@ -177,6 +177,7 @@ tr:nth-child(2n+1) {
Michael Bermanhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Michael Wall
Miguel Pereirahttp://sra.com";>SRA
International, IncET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ faganmMike Faganhttp://www.arcus-research.com";>Arcus ResearchMT (http://www.timeanddate.com/library/abbreviations/timezones/na/mst.html";>-7
/ http://www.timeanddate.com/library/abbreviations/timezones/na/mdt.html";>-6)
Morgan Haskel
Nguessan Kouame
Oren Falkowitzhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r903541 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot
Date: Tue Mar 25 16:55:27 2014
New Revision: 903541
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/bylaws.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 25 16:55:27 2014
@@ -1 +1 @@
-1581405
+1581416
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Tue Mar 25 16:55:27 2014
@@ -125,12 +125,14 @@ stability, and robustness of both code a
Deciding what is distributed as products of the Apache Accumulo
project.
Maintaining the project's shared resources, including the code repository,
mailing lists, and websites.
+Protecting and ensuring proper use of Apache trademarks by the project and
by other parties.
Speaking on behalf of the project.
Resolving license disputes regarding products of the project.
Nominating new PMC members and committers.
Maintaining these bylaws and other guidelines of the project.
-In particular, PMC members must understand both our project's criteria and
ASF criteria for voting on a http://www.apache.org/dev/release.html#management";>release.
+In particular, PMC members must understand both our project's criteria and
ASF criteria for voting on a http://www.apache.org/dev/release.html#management";>release.
+See the http://www.apache.org/dev/pmc.html";>PMC Guide for more
information on PMC responsibilities.
Membership of the PMC is by invitation only and must be approved by a
consensus approval of active PMC members. Upon acceptance of the invitation to
become a PMC member, it is the accepting memberâs responsibility to update
their status on the Accumulo web page accordingly.
A PMC member is considered emeritus, meaning inactive, by their own
declaration or by not contributing in any form to the project for over six
months. Emeritus members will be recognized by the PMC on the Accumulo web
page, in honor of their past contributions. Emeritus members retain all voting
and commit rights associated with their former designation and can move
themselves out of emeritus status by sending an announcement of their return to
the developer mailing list. It will be the returning member's responsibility to
update their status on the web page accordingly.
The chair of the PMC is appointed by the ASF board. The chair is an office
holder of the Apache Software Foundation (Vice President, Apache Accumulo) and
has primary responsibility to the board for the management of the projects
within the scope of the Accumulo PMC. The chair reports to the board quarterly
on developments within the Accumulo project.
@@ -239,7 +241,7 @@ stability, and robustness of both code a
No other voting actions are defined; all other actions should presume Lazy
Approval (defaulting to Consensus Approval upon veto). If an action is voted on
multiple times, or if a different approval type is desired, these bylaws should
be amended to include the action.
For the purposes of the "Adoption of New Codebase" action, the Accumulo
codebase is defined as the Accumulo site content, primary project code, and all
contributed code ("contribs") as they exist in their respective repositories.
Adoption of a new codebase generally refers to the creation of a new contrib
repository, but could cover, for example, a rework of the project site, or
merging a contrib project into the primary codebase.
-Voting actions for the removal of a committer or PMC member are
intentionally not defined. According to ASF rules, http://www.apache.org/dev/committers.html#committer-set-term";>committer
status never expires and http://www.apache.org/dev/pmc.html#pmc-removal";>the ASF board removes PMC
members.
+Voting actions for the removal of a committer or PMC member are
intentionally not defined. According to ASF rules, http://www.apache.org/dev/committers.html#committer-set-term";>committer
status never expires and http://www.apache.org/dev/pmc.html#pmc-removal";>PMC members can only be
removed with approval from the ASF Board.
Release Plans
The approval of a release plan begins the process of creating a new project
release. The process ends when a release candidate is approved.
An Accumulo release plan consists of at least the following:
svn commit: r903547 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Tue Mar 25 18:02:14 2014 New Revision: 903547 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 18:02:14 2014 @@ -1 +1 @@ -1581416 +1581434
svn commit: r903562 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Tue Mar 25 18:32:42 2014 New Revision: 903562 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 18:32:42 2014 @@ -1 +1 @@ -1581434 +1581455
svn commit: r903571 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Tue Mar 25 18:43:26 2014 New Revision: 903571 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 18:43:26 2014 @@ -1 +1 @@ -1581455 +1581459
svn commit: r903580 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Tue Mar 25 19:01:29 2014 New Revision: 903580 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Mar 25 19:01:29 2014 @@ -1 +1 @@ -1581459 +1581464
svn commit: r903752 - /websites/staging/accumulo/trunk/content/
Author: buildbot Date: Wed Mar 26 14:05:12 2014 New Revision: 903752 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 26 14:05:12 2014 @@ -1 +1 @@ -1581464 +1581847
svn commit: r903779 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Wed Mar 26 16:47:11 2014 New Revision: 903779 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 26 16:47:11 2014 @@ -1 +1 @@ -1581847 +1581925 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Wed Mar 26 16:47:11 2014 @@ -208,6 +208,28 @@ Jira issue ACCUMULO-12345 that affects 1 in the commit message: git commit -av + +Please include the ticket number at the beginning of the log message, and + in the first line, as it's easier to parse quickly. For example: +`ACCUMULO-2428 throw exception when rename fails after compaction` + + + +Consider following the git log message format described in + http://zachholman.com/talk/more-git-and-github-secrets/";>Zach Holman's talk + (specifically slides 78-98, beginning at 15:20 into the video). Essentially, + leave a short descriptive message in the first line, skip a line, and write + more detailed stuff there, if you need to. For example: +`ACCUMULO-2194 Add delay for randomwalk Security teardown` + +`If two Security randomwalk tests run back-to-back, the second test may see that the +table user still exists even though it was removed when the first test was torn down. +This can happen if the user drop does not propagate through Zookeeper quickly enough. +This commit adds a delay to the end of the Security test to give ZK some time.` + + + + Assuming others are developing against the version you also are, as you work, or before you create your patch, rebase your branch against the remote
svn commit: r903795 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Wed Mar 26 18:32:41 2014 New Revision: 903795 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Wed Mar 26 18:32:41 2014 @@ -1 +1 @@ -1581925 +1581991 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Wed Mar 26 18:32:41 2014 @@ -207,29 +207,20 @@ Jira issue ACCUMULO-12345 that affects 1 Make commits as you see fit as you fix the issue, referencing the issue name in the commit message: git commit -av - - Please include the ticket number at the beginning of the log message, and - in the first line, as it's easier to parse quickly. For example: -`ACCUMULO-2428 throw exception when rename fails after compaction` - - - +in the first line, as it's easier to parse quickly. For example: +ACCUMULO-2428 throw exception when rename fails after compaction Consider following the git log message format described in - http://zachholman.com/talk/more-git-and-github-secrets/";>Zach Holman's talk - (specifically slides 78-98, beginning at 15:20 into the video). Essentially, - leave a short descriptive message in the first line, skip a line, and write - more detailed stuff there, if you need to. For example: -`ACCUMULO-2194 Add delay for randomwalk Security teardown` - -`If two Security randomwalk tests run back-to-back, the second test may see that the -table user still exists even though it was removed when the first test was torn down. -This can happen if the user drop does not propagate through Zookeeper quickly enough. -This commit adds a delay to the end of the Security test to give ZK some time.` - - - - +http://zachholman.com/talk/more-git-and-github-secrets/";>Zach Holman's talk +(specifically slides 78-98, beginning at 15:20 into the video). Essentially, +leave a short descriptive message in the first line, skip a line, and write +more detailed stuff there, if you need to. For example: +ACCUMULO-2194 Add delay for randomwalk Security teardown +If two Security randomwalk tests run back-to-back, the second test may see that the +table user still exists even though it was removed when the first test was torn down. +This can happen if the user drop does not propagate through Zookeeper quickly enough. +This commit adds a delay to the end of the Security test to give ZK some time. + Assuming others are developing against the version you also are, as you work, or before you create your patch, rebase your branch against the remote
svn commit: r903939 - in /websites/staging/accumulo/trunk/content: ./ people.html
Author: buildbot
Date: Thu Mar 27 17:00:13 2014
New Revision: 903939
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/people.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 27 17:00:13 2014
@@ -1 +1 @@
-1581991
+1582400
Modified: websites/staging/accumulo/trunk/content/people.html
==
--- websites/staging/accumulo/trunk/content/people.html (original)
+++ websites/staging/accumulo/trunk/content/people.html Thu Mar 27 17:00:13 2014
@@ -148,6 +148,7 @@ tr:nth-child(2n+1) {
Aaron Glahehttp://www.data-tactics.com/>Data TaticsET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Al KrinkerET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Alex Moundalexishttp://www.cloudera.com";>ClouderaET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
+ Andrew George Wellshttp://clearedgeit.com/";>ClearEdgeITET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Arshak Navruzyanhttp://www.argyledata.com/";>Argyle Data
Chris Bennight
Chris McCubbinhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
@@ -177,7 +178,7 @@ tr:nth-child(2n+1) {
Michael Bermanhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
Michael Wall
Miguel Pereirahttp://sra.com";>SRA
International, IncET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
- faganmMike Faganhttp://www.arcus-research.com";>Arcus ResearchMT (http://www.timeanddate.com/library/abbreviations/timezones/na/mst.html";>-7
/ http://www.timeanddate.com/library/abbreviations/timezones/na/mdt.html";>-6)
+ Mike Faganhttp://www.arcus-research.com";>Arcus ResearchMT (http://www.timeanddate.com/library/abbreviations/timezones/na/mst.html";>-7
/ http://www.timeanddate.com/library/abbreviations/timezones/na/mdt.html";>-6)
Morgan Haskel
Nguessan Kouame
Oren Falkowitzhttp://sqrrl.com/>sqrrlET (http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5
/ http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4)
svn commit: r903959 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Thu Mar 27 21:11:10 2014 New Revision: 903959 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Thu Mar 27 21:11:10 2014 @@ -1 +1 @@ -1582400 +1582476 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Thu Mar 27 21:11:10 2014 @@ -127,7 +127,6 @@ stability, and robustness of both code a Maintaining the project's shared resources, including the code repository, mailing lists, and websites. Protecting and ensuring proper use of Apache trademarks by the project and by other parties. Speaking on behalf of the project. -Resolving license disputes regarding products of the project. Nominating new PMC members and committers. Maintaining these bylaws and other guidelines of the project.
svn commit: r904926 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Author: buildbot Date: Fri Apr 4 15:56:32 2014 New Revision: 904926 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/bylaws.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Apr 4 15:56:32 2014 @@ -1 +1 @@ -1582476 +1584773 Modified: websites/staging/accumulo/trunk/content/bylaws.html == --- websites/staging/accumulo/trunk/content/bylaws.html (original) +++ websites/staging/accumulo/trunk/content/bylaws.html Fri Apr 4 15:56:32 2014 @@ -91,7 +91,7 @@ Apache Accumulo Bylaws -This is version 0 of the bylaws. This draft has not yet been accepted by the Accumulo Project and only exists for voting purposes. +This is version 1 of the bylaws. Community work actively continues on the bylaws, and so key segments of them are subject to change. Introduction This document defines the bylaws under which the Apache Accumulo project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc. Accumulo is a project of the http://www.apache.org/foundation/";>Apache Software Foundation. The foundation holds the copyright on Apache code including the code in the Accumulo codebase. The http://www.apache.org/foundation/faq.html";>foundation FAQ explains the operation and background of the foundation. @@ -147,7 +147,7 @@ See the http://www.apache.org/d determine if a re-plan may be needed and, if so, call a vote call votes on release candidates -http://accumulo.apache.org/releasing.html";>Release guidelines and http://accumulo.apache.org/releasing.html";>details on the mechanics of creating an Accumulo release are available on the Accumulo project site. +http://accumulo.apache.org/governance/releasing.html";>Release guidelines and http://accumulo.apache.org/releasing.html";>details on the mechanics of creating an Accumulo release are available on the Accumulo project site. Decision Making Within the Accumulo project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'consensus approval'. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval. Voting
svn commit: r904947 - in /websites/staging/accumulo/trunk/content: ./ doap_Accumulo.rdf
Author: buildbot Date: Fri Apr 4 19:07:23 2014 New Revision: 904947 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/doap_Accumulo.rdf Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Apr 4 19:07:23 2014 @@ -1 +1 @@ -1584773 +1584867 Modified: websites/staging/accumulo/trunk/content/doap_Accumulo.rdf == Binary files - no diff available.
svn commit: r923623 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html
Author: buildbot
Date: Fri Sep 26 00:30:42 2014
New Revision: 923623
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/downloads/index.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 26 00:30:42 2014
@@ -1 +1 @@
-1627089
+1627683
Modified: websites/staging/accumulo/trunk/content/downloads/index.html
==
--- websites/staging/accumulo/trunk/content/downloads/index.html (original)
+++ websites/staging/accumulo/trunk/content/downloads/index.html Fri Sep 26
00:30:42 2014
@@ -271,26 +271,26 @@ $(function() { $.getJSON(mirrorURL + "?a
Be sure to verify your downloads by these https://www.apache.org/info/verification.html";
title="Verify">procedures using these https://www.apache.org/dist/accumulo/KEYS"; title="KEYS">KEYS.
Current Release
-1.6.0 latest
-The most recent Apache Accumulo™ release is version 1.6.0. See the release notes
and https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=06162580e885f11863d1a6d22f952bce35b78b68";
title="1.6.0 CHANGES">CHANGES.
-For convenience, https://www.apache.org/dist/accumulo/1.6.0/MD5SUM"; title="1.6.0 MD5 file
hashes">MD5 and https://www.apache.org/dist/accumulo/1.6.0/SHA1SUM"; title="1.6.0 SHA1
file hashes">SHA1 hashes are also available.
+1.6.1 latest
+The most recent Apache Accumulo™ release is version 1.6.1. See the
[release notes][REL_NOTES_160] and [CHANGES][CHANGES_160].
+For convenience, [MD5][MD5SUM_160] and [SHA1][SHA1SUM_160] hashes are also
available.
Generic Binaries
-https://www.apache.org/dyn/closer.cgi/accumulo/1.6.0/accumulo-1.6.0-bin.tar.gz";
link-suffix="/accumulo/1.6.0/accumulo-1.6.0-bin.tar.gz" onClick="return
trackOutboundLink('/downloads/accumulo-1.6.0-bin.tar.gz');">accumulo-1.6.0-bin.tar.gz
-https://www.apache.org/dist/accumulo/1.6.0/accumulo-1.6.0-bin.tar.gz.asc";>ASC
+https://www.apache.org/dyn/closer.cgi/accumulo/1.6.1/accumulo-1.6.1-bin.tar.gz";
link-suffix="/accumulo/1.6.1/accumulo-1.6.1-bin.tar.gz" onClick="return
trackOutboundLink('/downloads/accumulo-1.6.1-bin.tar.gz');">accumulo-1.6.1-bin.tar.gz
+https://www.apache.org/dist/accumulo/1.6.1/accumulo-1.6.1-bin.tar.gz.asc";>ASC
Source
-https://www.apache.org/dyn/closer.cgi/accumulo/1.6.0/accumulo-1.6.0-src.tar.gz";
link-suffix="/accumulo/1.6.0/accumulo-1.6.0-src.tar.gz" onClick="return
trackOutboundLink('/downloads/accumulo-1.6.0-src.tar.gz');">accumulo-1.6.0-src.tar.gz
-https://www.apache.org/dist/accumulo/1.6.0/accumulo-1.6.0-src.tar.gz.asc";>ASC
+https://www.apache.org/dyn/closer.cgi/accumulo/1.6.1/accumulo-1.6.1-src.tar.gz";
link-suffix="/accumulo/1.6.1/accumulo-1.6.1-src.tar.gz" onClick="return
trackOutboundLink('/downloads/accumulo-1.6.1-src.tar.gz');">accumulo-1.6.1-src.tar.gz
+https://www.apache.org/dist/accumulo/1.6.1/accumulo-1.6.1-src.tar.gz.asc";>ASC
1.6 Documentation
-https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=README;hb=06162580e885f11863d1a6d22f952bce35b78b68";
onClick="return trackOutboundLink('/1.6/README');">README
-http://search.maven.org/remotecontent?filepath=org/apache/accumulo/accumulo-docs/1.6.0/accumulo-docs-1.6.0-user-manual.pdf";
onClick="return trackOutboundLink('/1.6/accumulo_user_manual.pdf');">PDF
manual
+https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=README;hb=88c5473b3b49d797d3dabebd12fe517e9b248ba2";
onClick="return trackOutboundLink('/1.6/README');">README
+http://search.maven.org/remotecontent?filepath=org/apache/accumulo/accumulo-docs/1.6.1/accumulo-docs-1.6.1-user-manual.pdf";
onClick="return trackOutboundLink('/1.6/accumulo_user_manual.pdf');">PDF
manual
html
manual
examples
Javadoc
svn commit: r923624 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html
Author: buildbot
Date: Fri Sep 26 00:32:08 2014
New Revision: 923624
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/downloads/index.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 26 00:32:08 2014
@@ -1 +1 @@
-1627683
+1627684
Modified: websites/staging/accumulo/trunk/content/downloads/index.html
==
--- websites/staging/accumulo/trunk/content/downloads/index.html (original)
+++ websites/staging/accumulo/trunk/content/downloads/index.html Fri Sep 26
00:32:08 2014
@@ -272,8 +272,8 @@ $(function() { $.getJSON(mirrorURL + "?a
Be sure to verify your downloads by these https://www.apache.org/info/verification.html";
title="Verify">procedures using these https://www.apache.org/dist/accumulo/KEYS"; title="KEYS">KEYS.
Current Release
1.6.1 latest
-The most recent Apache Accumulo™ release is version 1.6.1. See the
[release notes][REL_NOTES_160] and [CHANGES][CHANGES_160].
-For convenience, [MD5][MD5SUM_160] and [SHA1][SHA1SUM_160] hashes are also
available.
+The most recent Apache Accumulo™ release is version 1.6.1. See the release notes
and https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=88c5473b3b49d797d3dabebd12fe517e9b248ba2";
title="1.6.1 CHANGES">CHANGES.
+For convenience, https://www.apache.org/dist/accumulo/1.6.1/MD5SUM"; title="1.6.1 MD5 file
hashes">MD5 and https://www.apache.org/dist/accumulo/1.6.1/SHA1SUM"; title="1.6.1 SHA1
file hashes">SHA1 hashes are also available.
Generic Binaries
svn commit: r923630 - in /websites/staging/accumulo/trunk/content: ./ apidocs/
Author: buildbot Date: Fri Sep 26 01:24:03 2014 New Revision: 923630 Log: Staging update by buildbot for accumulo Removed: websites/staging/accumulo/trunk/content/apidocs/ Modified: websites/staging/accumulo/trunk/content/ (props changed) Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 01:24:03 2014 @@ -1 +1 @@ -1627688 +1627689
svn commit: r923629 - in /websites/staging/accumulo/trunk/content: ./ apidocs/ apidocs/1.6/ apidocs/1.6/org/ apidocs/1.6/org/apache/ apidocs/1.6/org/apache/accumulo/ apidocs/1.6/org/apache/accumulo/cl
Author: buildbot Date: Fri Sep 26 01:23:11 2014 New Revision: 923629 Log: Staging update by buildbot for accumulo [This commit notification would consist of 1423 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.]
svn commit: r923635 - in /websites/staging/accumulo/trunk/content: ./ 1.6/apidocs/ extpaths.txt
Author: buildbot Date: Fri Sep 26 01:45:08 2014 New Revision: 923635 Log: Staging update by buildbot for accumulo Removed: websites/staging/accumulo/trunk/content/1.6/apidocs/ Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/extpaths.txt Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 01:45:08 2014 @@ -1 +1 @@ -1627691 +1627692 Modified: websites/staging/accumulo/trunk/content/extpaths.txt == --- websites/staging/accumulo/trunk/content/extpaths.txt (original) +++ websites/staging/accumulo/trunk/content/extpaths.txt Fri Sep 26 01:45:08 2014 @@ -1,2 +1,3 @@ 1.4/apidocs 1.5/apidocs +1.6/apidocs
svn commit: r923634 - in /websites/staging/accumulo/trunk/content: ./ 1.6/apidocs/ 1.6/apidocs/org/ 1.6/apidocs/org/apache/ 1.6/apidocs/org/apache/accumulo/ 1.6/apidocs/org/apache/accumulo/cluster/ 1.
Author: buildbot Date: Fri Sep 26 01:44:19 2014 New Revision: 923634 Log: Staging update by buildbot for accumulo [This commit notification would consist of 1423 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.]
svn commit: r923640 - in /websites/staging/accumulo/trunk/content: ./ doap_Accumulo.rdf
Author: buildbot Date: Fri Sep 26 02:07:45 2014 New Revision: 923640 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/doap_Accumulo.rdf Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 02:07:45 2014 @@ -1 +1 @@ -1627696 +1627698 Modified: websites/staging/accumulo/trunk/content/doap_Accumulo.rdf == Binary files - no diff available.
svn commit: r923642 - in /websites/staging/accumulo/trunk/content: ./ 1.6/apidocs/ extpaths.txt
Author: buildbot Date: Fri Sep 26 02:10:33 2014 New Revision: 923642 Log: Staging update by buildbot for accumulo Removed: websites/staging/accumulo/trunk/content/1.6/apidocs/ Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/extpaths.txt Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 02:10:33 2014 @@ -1 +1 @@ -1627698 +1627699 Modified: websites/staging/accumulo/trunk/content/extpaths.txt == --- websites/staging/accumulo/trunk/content/extpaths.txt (original) +++ websites/staging/accumulo/trunk/content/extpaths.txt Fri Sep 26 02:10:33 2014 @@ -1,2 +1,3 @@ 1.4/apidocs 1.5/apidocs +1.6/apidocs
svn commit: r923639 - in /websites/staging/accumulo/trunk/content: ./ 1.6/apidocs/ 1.6/apidocs/org/ 1.6/apidocs/org/apache/ 1.6/apidocs/org/apache/accumulo/ 1.6/apidocs/org/apache/accumulo/cluster/ 1.
Author: buildbot Date: Fri Sep 26 02:07:10 2014 New Revision: 923639 Log: Staging update by buildbot for accumulo [This commit notification would consist of 1423 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.]
svn commit: r923647 [1/2] - in /websites/staging/accumulo/trunk/content: ./ 1.4/examples/ 1.4/user_manual/ 1.5/examples/ 1.6/examples/ downloads/ example/ governance/ release_notes/ user_manual_1.3-in
Author: buildbot Date: Fri Sep 26 03:01:44 2014 New Revision: 923647 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/1.4/examples/batch.html websites/staging/accumulo/trunk/content/1.4/examples/bloom.html websites/staging/accumulo/trunk/content/1.4/examples/bulkIngest.html websites/staging/accumulo/trunk/content/1.4/examples/combiner.html websites/staging/accumulo/trunk/content/1.4/examples/constraints.html websites/staging/accumulo/trunk/content/1.4/examples/dirlist.html websites/staging/accumulo/trunk/content/1.4/examples/filedata.html websites/staging/accumulo/trunk/content/1.4/examples/filter.html websites/staging/accumulo/trunk/content/1.4/examples/helloworld.html websites/staging/accumulo/trunk/content/1.4/examples/index.html websites/staging/accumulo/trunk/content/1.4/examples/isolation.html websites/staging/accumulo/trunk/content/1.4/examples/mapred.html websites/staging/accumulo/trunk/content/1.4/examples/shard.html websites/staging/accumulo/trunk/content/1.4/examples/visibility.html websites/staging/accumulo/trunk/content/1.4/user_manual/Accumulo_Design.html websites/staging/accumulo/trunk/content/1.4/user_manual/Accumulo_Shell.html websites/staging/accumulo/trunk/content/1.4/user_manual/Administration.html websites/staging/accumulo/trunk/content/1.4/user_manual/Analytics.html websites/staging/accumulo/trunk/content/1.4/user_manual/Contents.html websites/staging/accumulo/trunk/content/1.4/user_manual/Development_Clients.html websites/staging/accumulo/trunk/content/1.4/user_manual/High_Speed_Ingest.html websites/staging/accumulo/trunk/content/1.4/user_manual/Introduction.html websites/staging/accumulo/trunk/content/1.4/user_manual/Security.html websites/staging/accumulo/trunk/content/1.4/user_manual/Shell_Commands.html websites/staging/accumulo/trunk/content/1.4/user_manual/Table_Configuration.html websites/staging/accumulo/trunk/content/1.4/user_manual/Table_Design.html websites/staging/accumulo/trunk/content/1.4/user_manual/Writing_Accumulo_Clients.html websites/staging/accumulo/trunk/content/1.4/user_manual/accumulo_user_manual.html websites/staging/accumulo/trunk/content/1.4/user_manual/index.html websites/staging/accumulo/trunk/content/1.5/examples/batch.html websites/staging/accumulo/trunk/content/1.5/examples/bloom.html websites/staging/accumulo/trunk/content/1.5/examples/bulkIngest.html websites/staging/accumulo/trunk/content/1.5/examples/classpath.html websites/staging/accumulo/trunk/content/1.5/examples/client.html websites/staging/accumulo/trunk/content/1.5/examples/combiner.html websites/staging/accumulo/trunk/content/1.5/examples/constraints.html websites/staging/accumulo/trunk/content/1.5/examples/dirlist.html websites/staging/accumulo/trunk/content/1.5/examples/export.html websites/staging/accumulo/trunk/content/1.5/examples/filedata.html websites/staging/accumulo/trunk/content/1.5/examples/filter.html websites/staging/accumulo/trunk/content/1.5/examples/helloworld.html websites/staging/accumulo/trunk/content/1.5/examples/index.html websites/staging/accumulo/trunk/content/1.5/examples/isolation.html websites/staging/accumulo/trunk/content/1.5/examples/mapred.html websites/staging/accumulo/trunk/content/1.5/examples/maxmutation.html websites/staging/accumulo/trunk/content/1.5/examples/regex.html websites/staging/accumulo/trunk/content/1.5/examples/rowhash.html websites/staging/accumulo/trunk/content/1.5/examples/shard.html websites/staging/accumulo/trunk/content/1.5/examples/tabletofile.html websites/staging/accumulo/trunk/content/1.5/examples/terasort.html websites/staging/accumulo/trunk/content/1.5/examples/visibility.html websites/staging/accumulo/trunk/content/1.6/examples/batch.html websites/staging/accumulo/trunk/content/1.6/examples/bloom.html websites/staging/accumulo/trunk/content/1.6/examples/bulkIngest.html websites/staging/accumulo/trunk/content/1.6/examples/classpath.html websites/staging/accumulo/trunk/content/1.6/examples/client.html websites/staging/accumulo/trunk/content/1.6/examples/combiner.html websites/staging/accumulo/trunk/content/1.6/examples/constraints.html websites/staging/accumulo/trunk/content/1.6/examples/dirlist.html websites/staging/accumulo/trunk/content/1.6/examples/export.html websites/staging/accumulo/trunk/content/1.6/examples/filedata.html websites/staging/accumulo/trunk/content/1.6/examples/filter.html websites/staging/accumulo/trunk/content/1.6/examples/helloworld.html websites/staging/accumulo/trunk/content/1.6/examples/index.html websites/staging/accumulo/trunk/content/1.6/examples/isolation.html websites/staging/accumulo/trunk/content/1.6/examples/mapred.html
svn commit: r923647 [2/2] - in /websites/staging/accumulo/trunk/content: ./ 1.4/examples/ 1.4/user_manual/ 1.5/examples/ 1.6/examples/ downloads/ example/ governance/ release_notes/ user_manual_1.3-in
Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html == --- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html (original) +++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html Fri Sep 26 03:01:44 2014 @@ -165,7 +165,7 @@ -Latest 1.6 release: 1.6.0 +Latest 1.6 release: 1.6.1 Latest 1.5 release: 1.5.1 Download Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Writing_Accumulo_Clients.html == --- websites/stag
svn commit: r923733 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.1.html
Author: buildbot
Date: Fri Sep 26 19:12:27 2014
New Revision: 923733
Log:
Staging update by buildbot for accumulo
Added:
websites/staging/accumulo/trunk/content/release_notes/1.6.1.html
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 26 19:12:27 2014
@@ -1 +1 @@
-1627705
+1627862
Added: websites/staging/accumulo/trunk/content/release_notes/1.6.1.html
==
--- websites/staging/accumulo/trunk/content/release_notes/1.6.1.html (added)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Fri Sep 26
19:12:27 2014
@@ -0,0 +1,352 @@
+
+
+
+
+
+
+
+
+
+
+
+
+ https://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"</a>;>
+
+
+
+
+
+ Apache Accumulo 1.5.2 Release Notes
+
+
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
+
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-50934829-1', 'apache.org');
+ ga('send', 'pageview');
+
+
+
+
+
+
+
+
+
+
+ Toggle navigation
+
+
+
+
+Accumulo
+
+
+
+
+
+Project
+
+
+Home
+Downloads
+Features
+http://www.apache.org/licenses/LICENSE-2.0";> License
+
+
+
+
+
+Community
+
+
+Get Involved
+Mailing Lists
+People
+https://blogs.apache.org/accumulo/";>Blog
+
+Governance
+Bylaws
+Consensus Building
+Lazy
Consensus
+Releasing
+Voting
+
+
+
+
+
+Development
+
+
+Source & Guide
+Git Workflow
+Contrib Projects
+Review Board
+Making Releases
+https://issues.apache.org/jira/browse/accumulo";> Issues
+https://builds.apache.org/view/A-D/view/Accumulo/";> Builds
+
+
+
+
+
+Documentation
+
+
+Manual
+1.5
+1.6
+
+Javadoc
+1.5
+1.6
+
+Examples
+1.5
+1.6
+
+Docs for Older
Verisons
+Screenshots
+Papers & Other Links
+Glossary
+
+
+
+
+
+ASF Links
+
+
+http://www.apache.org";> Apache
Software Foundation
+http://www.apache.org/foundation/sponsorship.html";> Sponsorship
+http://www.apache.org/security/";> Security
+http://www.apache.org/foundation/thanks.html";> Thanks
+
+
+
+
+http://search-hadoop.com/"; class="navbar-form
navbar-right" role="search">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Latest 1.6 release: 1.6.1
+Latest 1.5 release: 1.5.1
+
+Download
+
+
+
+https://twitter.com/apacheaccumulo";>@ApacheAccumulo
+https://www.linkedin.com/groups/Apache-Accumulo-Professionals-4554913";>Apache
Accumulo Professionals
+https://github.com/apache/accumulo";>apache /
accumulo
+#accumulo @ freenode
+http://blogs.apache.org/accumulo";>Apache Accumulo Blog
+
+
+http://accumulosummit.com/";>
+
+
+
+
+
+
+Apache Accumulo 1.5.2 Release Notes
+
+Apache Accumulo 1.5.2 is a maintenance release on the 1.5 version
branch.
+This release contains changes from over 100 issues, comprised of bug fixes
+(client side and server side), new test cases, and updated Hadoop support
+contributed by over 30 different contributors and committers.
+As this is a maintenance release, Apache Accumulo 1.5.2 has no client API
+incompatibilities over Apache Accumulo 1.5.0 and 1.5.1 and requires no manual
upgrade
+process. Users of 1.5.0 or 1.5.1 are strongly encouraged to update as soon as
possible
+to benefit from the improvements.
+Users who are new to Accumulo are encouraged to use a 1.6 release as opposed
+to the 1.5 line as development has already shifted towards the 1.6 line. For
those
+who cannot or do not want to upgrade to 1.6, 1.5.2 is still an excellent choice
+over earlier versions in the 1.5 line.
+Performance Improvements
+Apache Accumulo 1.5.2 includes a number of performance-related fixes over
previous versions.
+Write-Ahead Log sync performance
+The Write-Ahead Log (WAL) files are used to ensure durability of updates
made to Accumulo.
+A sync is called on the file in HDFS to make sure that the changes to the WAL
are persisted
+to disk, which allows Accumulo to recover in the case of failure. https://issues.apache.org/jira/browse/ACCUMULO-2766";>ACCUMULO-2766
fixed
+an issue where an operation against a WAL would unnecessarily wait for
multiple syncs, slowing
+down the ingest on the system.
+Minor-Compactions not
aggressive enough
+On
svn commit: r923739 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.1.html
Author: buildbot Date: Fri Sep 26 20:07:28 2014 New Revision: 923739 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 20:07:28 2014 @@ -1 +1 @@ -1627862 +1627870 Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.6.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Fri Sep 26 20:07:28 2014 @@ -192,20 +192,15 @@ Latest 1.5 release: 1.5.1Apache Accumulo 1.5.2 Release Notes -Apache Accumulo 1.5.2 is a maintenance release on the 1.5 version branch. -This release contains changes from over 100 issues, comprised of bug fixes -(client side and server side), new test cases, and updated Hadoop support -contributed by over 30 different contributors and committers. -As this is a maintenance release, Apache Accumulo 1.5.2 has no client API -incompatibilities over Apache Accumulo 1.5.0 and 1.5.1 and requires no manual upgrade -process. Users of 1.5.0 or 1.5.1 are strongly encouraged to update as soon as possible -to benefit from the improvements. -Users who are new to Accumulo are encouraged to use a 1.6 release as opposed -to the 1.5 line as development has already shifted towards the 1.6 line. For those -who cannot or do not want to upgrade to 1.6, 1.5.2 is still an excellent choice -over earlier versions in the 1.5 line. +Apache Accumulo 1.6.1 is a maintenance release on the 1.6 version branch. +This release contains changes from over 175 issues, comprised of bug-fixes, performance +improvements and better test cases. As this is a maintenance release, Apache Accumulo +1.6.1 has no client API incompatibilities over Apache Accumulo 1.6.0. Users of 1.6.0 +are strongly encouraged to update as soon as possible to benefit from the improvements. +New users are encouraged to use this release over 1.6.0 or any other older releases. Performance Improvements -Apache Accumulo 1.5.2 includes a number of performance-related fixes over previous versions. +Apache Accumulo 1.6.1 includes a number of performance-related fixes over previous versions. +Many of these improvements were also included in the recently released Apache Accumulo 1.5.2. Write-Ahead Log sync performance The Write-Ahead Log (WAL) files are used to ensure durability of updates made to Accumulo. A sync is called on the file in HDFS to make sure that the changes to the WAL are persisted @@ -238,27 +233,23 @@ that lets users to change the HDFS sync of hsync may result in about a 30% increase in ingest performance. For users upgrading from Hadoop-1 or Hadoop-0.20 releases, hflush is the equivalent of how sync was implemented in these older versions of Hadoop and should give comparable performance. -Server-side mutation queue size -When users desire writes to be as durable as possible, using hsync, the ingest performance -of the system can be improved by increasing the tserver.mutation.queue.max property. The cost -of this change is that it will cause TabletServers to use additional memory per writer. In 1.5.1, -the value of this parameter defaulted to a conservative 256K, which resulted in sub-par ingest -performance. -1.5.2 and https://issues.apache.org/jira/browse/ACCUMULO-3018";>ACCUMULO-3018 increases this buffer to 1M which has a noticeable positive impact on -ingest performance with a minimal increase in TabletServer memory usage. +Other improvements +Use of Hadoop CredentialProviders +Apache Hadoop 2.6.0 introduced a new API aimed at providing ways to separate sensitive values +from being stored in plaintext as a part of https://issues.apache.org/jira/browse/HADOOP-10607";>HADOOP-10607. Accumulo has had two sensitive +configuration properties stored in accumulo-site.xml for every standard installation: instance.secret +and trace.token.property.password. If either of these properties are compromised, it could lead to +unwanted access of Accumulo. https://issues.apache.org/jira/browse/ACCUMULO-2464";>ACCUMULO-2464 modifies Accumulo so that it can stored any sensitive +configuration properties in a Hadoop CredentialProvider. With sensitive values removed from accumulo-site.xml, +it can be shared without concern and security can be focused solely on the CredentialProvider. Notable Bug Fixes -Fixes MapReduce package name change -1.5.1 inadvertently included a change to RangeInputSplit which created an incompatibility -with 1.5.0. The original class has been restored to ensure that users accessing -the RangeInputSplit class do not have to alter thei
svn commit: r923741 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.1.html
Author: buildbot Date: Fri Sep 26 20:10:57 2014 New Revision: 923741 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 20:10:57 2014 @@ -1 +1 @@ -1627870 +1627873 Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.6.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Fri Sep 26 20:10:57 2014 @@ -34,7 +34,7 @@ - Apache Accumulo 1.5.2 Release Notes + Apache Accumulo 1.6.1 Release Notes
svn commit: r923742 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.1.html
Author: buildbot Date: Fri Sep 26 20:18:07 2014 New Revision: 923742 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Sep 26 20:18:07 2014 @@ -1 +1 @@ -1627873 +1627878 Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.1.html == --- websites/staging/accumulo/trunk/content/release_notes/1.6.1.html (original) +++ websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Fri Sep 26 20:18:07 2014 @@ -274,7 +274,7 @@ constraint no longer hangs the entire sy never came online. https://issues.apache.org/jira/browse/ACCUMULO-2974";>ACCUMULO-2974 fixes an issue from the change of file references stored as absolute paths instead of relative paths in the Accumulo metadata table. Guava dependency changed -https://issues.apache.org/jira/browse/ACCUMULO-3100";>ACCUMULO-3100 lowered the dependency on Guava from 15.0.1 to 14.0. This dependency +https://issues.apache.org/jira/browse/ACCUMULO-3100";>ACCUMULO-3100 lowered the dependency on Guava from 15.0 to 14.0.1. This dependency now matches what Hadoop is depending on for the 2.x.y version line. Depending on a newer version of Guava introduces many issues stemming from deprecated classes in use by Hadoop which have been removed. While installations of Accumulo will likely work as expected with
svn commit: r923775 - in /websites/staging/accumulo/trunk/content: ./ git.html
Author: buildbot Date: Sat Sep 27 03:12:12 2014 New Revision: 923775 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/git.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Sat Sep 27 03:12:12 2014 @@ -1 +1 @@ -1627878 +1627921 Modified: websites/staging/accumulo/trunk/content/git.html == --- websites/staging/accumulo/trunk/content/git.html (original) +++ websites/staging/accumulo/trunk/content/git.html Sat Sep 27 03:12:12 2014 @@ -295,8 +295,8 @@ Jira issue ACCUMULO-12345 that affects 1 For the given issue you intend to work on, choose the 'lowest' fixVersion - and create a branch for yourself to work in. This example is against fixVersion 1.5.2. -git checkout -b ACCUMULO-12345-my-work origin/1.5.2-SNAPSHOT + and create a branch for yourself to work in. This example is against the next release of 1.5 +git checkout -b ACCUMULO-12345-my-work origin/1.5 Make commits as you see fit as you fix the issue, referencing the issue name @@ -320,12 +320,12 @@ This commit adds a delay to the end of t Assuming others are developing against the version you also are, as you work, or before you create your patch, rebase your branch against the remote to lift your changes to the top of your branch. The branch specified here should be the same one you used in step 4. -git pull --rebase origin 1.5.2-SNAPSHOT +git pull --rebase origin 1.5 At this point, you can create a patch file from the upstream branch to attach to the ACCUMULO-12345 Jira issue. The branch specified here should be teh same one you used in step 4. -git format-patch --stdout origin/1.5.2-SNAPSHOT > ACCUMULO-12345.patch +git format-patch --stdout origin/1.5 > ACCUMULO-12345.patch An alternative to creating a patch is submitting a request to pull your changes @@ -346,25 +346,11 @@ free of unnecessary merges. Developers Primary Development Primary development should take place in master which is to contain the most -recent, un-released version of Apache Accumulo. -For changes staged for the next minor release of Apache Accumulo, it has been -suggested that a branch is created for the purpose of containing the bug-fixes, -API-compatible improvements and backported-features. This provides the -following: - -Avoids many long-running 'SNAPSHOT' branches to force the developer to best - consider where his/her changes should be applied. -Better ties a branch containing commits for a minor release to Jira issues - fixed in said minor release. - -If said short-lived branch doesn't yet exist, the developer should create said -branch off of the last minor release in the targeted major version. -For example, if a developer finds a fix that needs to be made against the 1.4.3 -release of Apache Accumulo, the developer should create a new branch from the -1.4.3 tag, apply the changes, and push the branch remotely with an appropriate -name. It has been suggested to name the branch in the same manner in which -Maven releases are named. In other words, the branch just created would be -named 1.4.4-snapshot or similar. +recent, un-released version of Apache Accumulo. Branches exist for minor releases +for each previously released major version. +Using long-lived branches that track a major release line simplifies management and +release practices. Developers are encouraged to make branches for their own purposes, +for large features, release candidates or whatever else is deemed useful. Reviewing contributor changes It is always the responsibility of committers to determine that a patch is intended and able to be contributed. From the @@ -383,8 +369,8 @@ list of commits sent to the Accumulo dev contributors: -Checkout the branch which the patch is submitted for: -git checkout 1.5.1-SNAPSHOT +Checkout the branch for the major version which the patch is intended: +git checkout 1.5 Verify the changes introduced by the patch: @@ -400,11 +386,11 @@ contributors: When finished, push the changes: -git push origin 1.5.1-SNAPSHOT +git push origin 1.5 Merge where appropriate: -git checkout master && git merge 1.5.1-SNAPSHOT +git checkout master && git merge 1.5 Github Pull-Requests @@ -536,17 +522,19 @@ next minor release is '1.6.1'. These cha client code which works against z and should absolutely not change the public API. By convention, the branch containing the changes z' should be named -x.y.z'-SNAPSHOT. The steps to take are as follows: +x.y (where the changes for z' are commits since x.y.z. The steps to take are as follows: Prepare the release candidate. Release Guide, Maven
svn commit: r924532 - in /websites/staging/accumulo/trunk/content: ./ 1.6/accumulo_user_manual.html
Author: buildbot
Date: Fri Oct 3 16:22:57 2014
New Revision: 924532
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
Propchange: websites/staging/accumulo/trunk/content/
--
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 3 16:22:57 2014
@@ -1 +1 @@
-1627921
+1629249
Modified: websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
==
--- websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
(original)
+++ websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html Fri
Oct 3 16:22:57 2014
@@ -548,6 +548,8 @@ span.icon > [class^="icon-"], span.icon
11.5.3. Cluster Specification
11.5.4. Accumulo Settings
11.5.5. Deploy Configuration
+11.5.6 Sensitive Configuration
Values
+11.5.7.
Using a JavaKeyStoreCredentialProvider for storage
11.6. Initialization
@@ -597,7 +599,8 @@ span.icon > [class^="icon-"], span.icon
13.8.2. ZooKeeper Failure
-13.9. File Naming Conventions
+13.9. Upgrade Issues
+13.10. File Naming Conventions
14. Appendix A: Configuration Management
@@ -1296,6 +1299,17 @@ Instance inst = new ZooKeeperInstance(in
Connector conn = inst.getConnector("user", new
PasswordToken("passwd"));
+
+The PasswordToken is the most common implementation of an
AuthenticationToken.
+This general interface allows authentication as an Accumulo user to come from
a variety of sources
+or means. The CredentialProviderToken leverages the Hadoop CredentialProviders
(new in Hadoop 2.6).
+
+
+For example, the CredentialProviderToken can be used in conjunction with a
Java KeyStore
+to alleviate passwords stored in cleartext. When stored in HDFS, a single
KeyStore can be
+used across an entire instance. Be aware that KeyStores stored on the local
filesystem
+must be made available to all nodes in the Accumulo cluster.
+
4.3. Writing Data
@@ -1405,10 +1419,10 @@ Scanner scan =
conn.createScanner("table", auths);
scan.setRange(new Range("harry","john"));
-scan.fetchFamily("attributes");
+scan.fetchColumnFamily(new Text("attributes"));
for(Entry<Key,Value> entry : scan) {
-String row = entry.getKey().getRow();
+Text row = entry.getKey().getRow();
Value value = entry.getValue();
}
@@ -1478,7 +1492,7 @@ TabletServers in parallel.
BatchScanner bscan =
conn.createBatchScanner("table", auths, 10);
bscan.setRanges(ranges);
-bscan.fetchFamily("attributes");
+bscan.fetchColumnFamily(new Text("attributes"));
for(Entry<Key,Value> entry : scan) {
System.out.println(entry.getValue());
@@ -1944,6 +1958,14 @@ config -t mytable -s table.iterator.minc
config -t mytable -s
table.iterator.majc.myiter.opt.myoptionname=myoptionvalue
+
+Typically, a table will have multiple iterators. Accumulo configures a set
of
+system level iterators for each table. These iterators provide core
functionality
+like visibility label filtering and may not be removed by users. User level
iterators
+are applied in the order of their priority. Priority is a user-configured
integer;
+iterators with lower numbers go first, passing the results of their iteration
on
+to the other iterators up the stack.
+
6.4.2. Setting Iterators
Programmatically
@@ -3569,8 +3591,14 @@ mutation.put(colFam, colQual, colVis, ti
Security labels consist of a set of user-defined tokens that are required
to read the
value the label is associated with. The set of tokens required can be
specified using
-syntax that supports logical AND and OR combinations of tokens, as well as
nesting
-groups of tokens together.
+syntax that supports logical AND & and OR |
combinations of tokens, as well as nesting
+groups () of tokens together.
+
+
+Each term is comprised of one to many alpha-numeric characters, hyphens,
underscores
+or periods. Optionally, each term may be wrapped in quotation marks which
removes the
+restriction on valid characters. In quoted terms, quotation marks and
backslash characters
+can be used as characters in the term by escaping them with a backslash.
For example, suppose within our organization we want to label our data
values with
@@ -3926,17 +3954,20 @@ native map also avoids the performance i
in the JVM by causing it to pause much less frequently.
-32-bit and 64-bit Linux versions of the native map ship with the Accumulo
dist package.
-For other operating systems, the native map can be built from the codebase in
two ways-
-from maven or from the Makefile.
+32-bit and 64-bit Linux and Mac OS X versions of the native map can be
built from the
+Accumulo bin package
svn commit: r925748 - in /websites/staging/accumulo/trunk/content: ./ downloads/index.html
Author: buildbot Date: Tue Oct 14 15:01:57 2014 New Revision: 925748 Log: Staging update by buildbot for accumulo Modified: websites/staging/accumulo/trunk/content/ (props changed) websites/staging/accumulo/trunk/content/downloads/index.html Propchange: websites/staging/accumulo/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Oct 14 15:01:57 2014 @@ -1 +1 @@ -1629249 +1631778 Modified: websites/staging/accumulo/trunk/content/downloads/index.html == --- websites/staging/accumulo/trunk/content/downloads/index.html (original) +++ websites/staging/accumulo/trunk/content/downloads/index.html Tue Oct 14 15:01:57 2014 @@ -198,6 +198,7 @@ Latest 1.5 release: 1.5.1
