accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r951775 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.7.0.html
Date Mon, 18 May 2015 20:08:00 GMT
Author: buildbot
Date: Mon May 18 20:08:00 2015
New Revision: 951775

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/release_notes/1.7.0.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon May 18 20:08:00 2015
@@ -1 +1 @@
-1680083
+1680085

Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.7.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.0.html Mon May 18 20:08:00 2015
@@ -289,9 +289,19 @@ were also added to the shell to specify
 specify an arbitraty compaction strategy is mutually exclusive with the file selection 
 options and file creation options.</p>
 <h3 id="api-clarification">API Clarification</h3>
-<p>The declared API in 1.6.x was incomplete.   Some important classes like ColumnVisibility
were not declared as Accumulo API.  A lot of work was done under <a href="https://issues.apache.org/jira/browse/ACCUMULO-3657">ACCUMULO-3657</a>
to correct the API statement and clean up the API.  The expanded  and simplified API statement
is in the <a href="https://github.com/apache/accumulo/blob/8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d/README.md">README</a>.</p>
-<p>In some places in the API, non API types were used.  Ideally public API members
would only use public API types.  A tool called <a href="http://code.revelc.net/apilyzer-maven-plugin/">APILyzer</a>
was created to find all API members that used non-API types.  Many of the violations found
by this tool were deprecated to clearly communicate that a non API type was used.  For example,
a few public API methods returned a class called KeyExtent.  KeyExtent was never intended
to be in the public API, it contains a lot of code related to Accumulo internals.   KeyExtent
and the API methods returning it were deprecated.  These were replaced with a new way of identifying
tablets that does not expose internals.  Deprecating a type like this from the API makes the
API more stable and makes it easier for contributors to change Accumulo internals w/o impacting
the API.</p>
-<p>Created an Accumulo API regular expression for use with checkstyle.  Starting with
1.7.0, projects building on Accumulo can use this checkstyle rule to ensure they are only
using Accumulo's public API.  The regular expression can be found in the <a href="https://github.com/apache/accumulo/blob/8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d/README.md">README</a>.</p>
+<p>The declared API in 1.6.x was incomplete. Some important classes like ColumnVisibility
were not declared as Accumulo API. A lot 
+of work was done under <a href="https://issues.apache.org/jira/browse/ACCUMULO-3657">ACCUMULO-3657</a>
to correct the API statement and clean up the API. The expanded and 
+simplified API statement is in the <a href="https://github.com/apache/accumulo/blob/8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d/README.md">README</a>.</p>
+<p>In some places in the API, non API types were used. Ideally public API members would
only use public API types. A tool called 
+<a href="http://code.revelc.net/apilyzer-maven-plugin/">APILyzer</a> was created
to find all API members that used non-API types. Many of the violations found by this tool
were 
+deprecated to clearly communicate that a non API type was used. For example, a few public
API methods returned a class called 
+KeyExtent. KeyExtent was never intended to be in the public API, it contains a lot of code
related to Accumulo internals. KeyExtent 
+and the API methods returning it were deprecated. These were replaced with a new way of identifying
tablets that does not expose 
+internals. Deprecating a type like this from the API makes the API more stable and makes
it easier for contributors to change 
+Accumulo internals w/o impacting the API.</p>
+<p>Created an Accumulo API regular expression for use with checkstyle. Starting with
1.7.0, projects building on Accumulo can use 
+this checkstyle rule to ensure they are only using Accumulo's public API. The regular expression
can be found in the 
+<a href="https://github.com/apache/accumulo/blob/8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d/README.md">README</a>.</p>
 <h3 id="balancing-groups-of-tablets">Balancing Groups of Tablets</h3>
 <p>By default Accumulo evenly spreads each tables tablets across a cluster.  In some

 situations its advantageous for query or ingest to evenly spreads groups of tablets 



Mime
View raw message