accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ktur...@apache.org
Subject [accumulo-website] branch master updated: update 2.0 release notes
Date Thu, 01 Aug 2019 17:44:53 GMT
This is an automated email from the ASF dual-hosted git repository.

kturner pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 75b8b87  update 2.0 release notes
75b8b87 is described below

commit 75b8b87f373b02f3d99c8d2639f817a46715bd57
Author: Keith Turner <kturner@apache.org>
AuthorDate: Thu Aug 1 13:44:34 2019 -0400

    update 2.0 release notes
---
 _posts/release/2017-09-05-accumulo-2.0.0.md | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/_posts/release/2017-09-05-accumulo-2.0.0.md b/_posts/release/2017-09-05-accumulo-2.0.0.md
index 720aaaf..3ab0deb 100644
--- a/_posts/release/2017-09-05-accumulo-2.0.0.md
+++ b/_posts/release/2017-09-05-accumulo-2.0.0.md
@@ -25,12 +25,13 @@ that ships with the Accumulo tarball. The new API has the following benefits
ove
   * Clients can now be created with default settings for `BatchWriter`, `Scanner`, etc.
 See the [client documentation][clients] for more information on how to use the new API.
 
-### Hadoop 3 and Java 8.
+### Hadoop 3 Java 8 & 11.
 
 Accumulo 2.x expects at least Java 8 and Hadoop 3.  It is built against Java 8
 and Hadoop 3 and the binary tarball is targeted to work with a Java 8 and
 Hadoop 3 system.  See {% jira ACCUMULO-4826 %},  {% ghi 531 %}, and {% jira
-ACCUMULO-4299 %}.
+ACCUMULO-4299 %}.  Running with Java 11 is also supported, but Java 11 is not
+required.
 
 ### Simplified Accumulo scripts and configuration files
 
@@ -70,8 +71,11 @@ TODO link to javadoc for new API. See {% ghi 436 %}, {% ghi 472 %}, and
{% ghi 5
 [Summaries]({% durl development/summaries %}) enables continually generating
 statistics about a table with user defined functions.  This feature can inform
 a user about what is in their table and be used by compaction strategies to
-make decisions.  For example, using this feature it would be possible to compact
-all tablets where deletes are more than 25% of the data.
+make decisions.  For example, using this feature it would be possible to
+compact all tablets where deletes are more than 25% of the data. Another
+example use case is optimizing filtering compactions by enabling smart
+selection of files with pertinent data. Examples of filtering compactions are
+age off and removal of non-compliant data.
 
 ### Scan Executors
 
@@ -80,6 +84,15 @@ and dedicating scan resources. Each executor has a configurable number
of
 threads and an optional custom prioritizer.  Tables can be configured in a
 flexible way to dispatch scans to different executors.
 
+### SPI package
+
+All new pluggable components introduced in 2.0 were placed under a new SPI
+package.  The SPI package is analyzed by [Apilyzer] at build time to ensure
+plugins only use SPI and API types.  This prevents plugins from using internal
+Accumulo types that are inherently unstable over time.  Plugins created before
+2.0 do use internal types and are less stable.  The new pluggable interfaces
+should be much more stable.
+
 ### Official Accumulo docker image was created
 
 An [official Accumulo docker images][accumulo-docker] was created in [ACCUMULO-4706] to make
@@ -187,3 +200,4 @@ View the [Upgrading Accumulo documentation][upgrade] for guidance.
 [ACCUMULO-4449]: https://issues.apache.org/jira/browse/ACCUMULO-4449
 [ACCUMULO-3652]: https://issues.apache.org/jira/browse/ACCUMULO-3652
 [#634]: https://github.com/apache/accumulo/issues/634
+[Apilyzer]: https://code.revelc.net/apilyzer-maven-plugin/


Mime
View raw message