Author: bhavanki
Date: Tue Apr 15 19:17:15 2014
New Revision: 1587698
URL: http://svn.apache.org/r1587698
Log:
Merged trunk into redesign14 branch - bylaws version 2, draft 1.6.0 relnotes.
Modified:
accumulo/site/branches/redesign14/ (props changed)
accumulo/site/branches/redesign14/content/bylaws.mdtext
accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext
Propchange: accumulo/site/branches/redesign14/
------------------------------------------------------------------------------
Merged /accumulo/site/trunk:r1579718,1586320-1587258
Modified: accumulo/site/branches/redesign14/content/bylaws.mdtext
URL:
http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/bylaws.mdtext?rev=1587698&r1=1587697&r2=1587698&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/bylaws.mdtext (original)
+++ accumulo/site/branches/redesign14/content/bylaws.mdtext Tue Apr 15 19:17:15
2014
@@ -17,7 +17,7 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-This is version 1 of the bylaws. Community work actively continues on the
bylaws, and so key segments of them are subject to change.
+This is version 2 of the bylaws. Community work actively continues on the
bylaws, and so key segments of them are subject to change.
# Introduction
@@ -126,7 +126,14 @@ Decisions regarding the project are made
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.
+See the [voting page](http://accumulo.apache.org/governance/voting.html) for
more details on the mechanics of voting.
+
+<a name="CTR"></a>
+## Commit Then Review (CTR)
+
+Voting can also be applied to changes to the Accumulo codebase. Under the
Commit Then Review policy, committers can make changes to the codebase without
seeking approval beforehand, and the changes are assumed to be approved unless
an objection is raised. Only if an objection is raised must a vote take place
on the code change.
+
+For some code changes, committers may wish to get feedback from the community
before making the change. It is acceptable for a committer to seek approval
before making a change if they so desire.
## Approvals
@@ -140,7 +147,7 @@ These are the types of approvals that ca
<tr><td>Majority Approval</td>
<td>A majority approval vote passes with 3 binding +1 votes and more
binding +1 votes than -1 votes.</td>
<tr><td>Lazy Approval (or Lazy Consensus)</td>
- <td>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.</td>
+ <td>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. Lazy Approval can be either
<em>stated</em> or <em>assumed</em>, as detailed on the <a
href="/governance/lazyConsensus.html">lazy consensus page</a>.</td>
</table>
## Vetoes
@@ -153,6 +160,8 @@ If you disagree with a valid veto, you m
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.
+For Code Change actions, a committer may choose to employ assumed or stated
Lazy Approval under the [CTR](#CTR) policy. Assumed Lazy Approval has no
minimum length of time before the change can be made.
+
<table class="table">
<tr><th>Action</th>
<th>Description</th>
Modified: accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext
URL:
http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext?rev=1587698&r1=1587697&r2=1587698&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext
(original)
+++ accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext Tue
Apr 15 19:17:15 2014
@@ -20,8 +20,6 @@ Notice: Licensed to the Apache Softwa
Apache Accumulo 1.6.0 adds some major new features and fixes many bugs. This
release contains changes from 609 issues contributed by 36 contributors and
committers.
-TODO paragraph on API changes
-
Accumulo 1.6.0 runs on Hadoop 1, however Hadoop 2 with HA namenode is
recommended for production systems. In addition to HA, Hadoop 2 also offers
better data durability guarantees, in the case when nodes lose power, than
Hadoop 1.
## Notable Improvements
@@ -155,6 +153,18 @@ For more information, see [ACCUMULO-1950
* [ACCUMULO-2441][ACCUMULO-2441] Document internal state stored in RFile names
* [ACCUMULO-2590][ACCUMULO-2590] Update public API in readme to clarify
what's included
+## API Changes
+
+The following deprecated methods were removed in [ACCUMULO-1533][ACCUMULO-1533]
+
+ * Many map reduce methods deprecated in [ACCUMULO-769][ACCUMULO-769] were
removed
+ * `SecurityErrorCode
o.a.a.core.client.AccumuloSecurityException.getErrorCode()` *deprecated in
[ACCUMULO-970][ACCUMULO-970]*
+ * `Connector o.a.a.core.client.Instance.getConnector(AuthInfo)` *deprecated
in [ACCUMULO-1024][ACCUMULO-1024]*
+ * `Connector o.a.a.core.client.ZooKeeperInstance.getConnector(AuthInfo)`
*deprecated in [ACCUMULO-1024][ACCUMULO-1024]*
+ * `static String
o.a.a.core.client.ZooKeeperInstance.getInstanceIDFromHdfs(Path)` *deprecated in
[ACCUMULO-1][ACCUMULO-1]*
+ * `static String ZooKeeperInstance.lookupInstanceName (ZooCache,UUID)`
*deprecated in [ACCUMULO-765][ACCUMULO-765]*
+ * `void o.a.a.core.client.ColumnUpdate.setSystemTimestamp(long)` *deprecated
in [ACCUMULO-786][ACCUMULO-786]*
+
## Testing
Below is a list of all platforms that 1.6.0 was tested against by developers.
Each Apache Accumulo release
@@ -180,19 +190,25 @@ and, in HDFS High-Availability instances
</tr>
</table>
+[ACCUMULO-1]: https://issues.apache.org/jira/browse/ACCUMULO-1
[ACCUMULO-112]: https://issues.apache.org/jira/browse/ACCUMULO-112 "Partition
data in memory by locality group"
[ACCUMULO-118]: https://issues.apache.org/jira/browse/ACCUMULO-118 "Multiple
namenode support"
[ACCUMULO-324]: https://issues.apache.org/jira/browse/ACCUMULO-324
"System/site constraints and iterators should NOT affect the METADATA table"
[ACCUMULO-335]: https://issues.apache.org/jira/browse/ACCUMULO-335 "Batch
scanning over the !METADATA table can cause issues"
[ACCUMULO-391]: https://issues.apache.org/jira/browse/ACCUMULO-391
"Multi-table input format"
+[ACCUMULO-765]: https://issues.apache.org/jira/browse/ACCUMULO-765
+[ACCUMULO-769]: https://issues.apache.org/jira/browse/ACCUMULO-769
+[ACCUMULO-786]: https://issues.apache.org/jira/browse/ACCUMULO-786
[ACCUMULO-802]: https://issues.apache.org/jira/browse/ACCUMULO-802 "Table
namespaces"
[ACCUMULO-842]: https://issues.apache.org/jira/browse/ACCUMULO-842 "Add FATE
administration to shell"
[ACCUMULO-958]: https://issues.apache.org/jira/browse/ACCUMULO-958 "Support
pluggable encryption in walogs"
[ACCUMULO-998]: https://issues.apache.org/jira/browse/ACCUMULO-998 "Support
encryption at rest"
+[ACCUMULO-970]: https://issues.apache.org/jira/browse/ACCUMULO-970
[ACCUMULO-980]: https://issues.apache.org/jira/browse/ACCUMULO-980 "Support
pluggable codecs for RFile"
[ACCUMULO-1000]: https://issues.apache.org/jira/browse/ACCUMULO-1000
"Conditional Mutations"
[ACCUMULO-1009]: https://issues.apache.org/jira/browse/ACCUMULO-1009 "Support
encryption over the wire"
[ACCUMULO-1018]: https://issues.apache.org/jira/browse/ACCUMULO-1018 "Client
does not give informative message when user can not read table"
+[ACCUMULO-1024]: https://issues.apache.org/jira/browse/ACCUMULO-1024
[ACCUMULO-1218]: https://issues.apache.org/jira/browse/ACCUMULO-1218 "document
the recovery from a failed zookeeper"
[ACCUMULO-1336]: https://issues.apache.org/jira/browse/ACCUMULO-1336 "Add
lexicoders from Typo to Accumulo"
[ACCUMULO-1375]: https://issues.apache.org/jira/browse/ACCUMULO-1375 "Update
README files in proxy module."
@@ -203,6 +219,7 @@ and, in HDFS High-Availability instances
[ACCUMULO-1481]: https://issues.apache.org/jira/browse/ACCUMULO-1481 "Root
tablet in its own table"
[ACCUMULO-1492]: https://issues.apache.org/jira/browse/ACCUMULO-1492
"bin/accumulo should follow symbolic links"
[ACCUMULO-1507]: https://issues.apache.org/jira/browse/ACCUMULO-1507 "Dynamic
Classloader still can't keep proper track of jars"
+[ACCUMULO-1533]: https://issues.apache.org/jira/browse/ACCUMULO-1533
[ACCUMULO-1585]: https://issues.apache.org/jira/browse/ACCUMULO-1585 "Use node
addresses from config files verbatim"
[ACCUMULO-1562]: https://issues.apache.org/jira/browse/ACCUMULO-1562 "add a
troubleshooting section to the user guide"
[ACCUMULO-1566]: https://issues.apache.org/jira/browse/ACCUMULO-1566 "Add
ability for client to start Scanner readahead immediately"
@@ -246,7 +263,7 @@ and, in HDFS High-Availability instances
[ACCUMULO-2495]: https://issues.apache.org/jira/browse/ACCUMULO-2495 "OOM
exception didn't bring down tserver"
[ACCUMULO-2519]: https://issues.apache.org/jira/browse/ACCUMULO-2519 "FATE
operation failed across upgrade"
[ACCUMULO-2590]: https://issues.apache.org/jira/browse/ACCUMULO-2590 "Update
public API in readme to clarify what's included"
-
+[ACCUMULO-2659]: https://issues.apache.org/jira/browse/ACCUMULO-2659
[1]: http://research.google.com/archive/bigtable.html
[2]:
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.44.2782&rep=rep1&type=pdf
