svn commit: r1680399 - /accumulo/site/trunk/content/release_notes/1.7.0.mdtext

[el...@apache.org]

Author: elserj
Date: Tue May 19 21:45:17 2015
New Revision: 1680399

URL: http://svn.apache.org/r1680399
Log:
ACCUMULO-3737 Includes docs for previously mentioned issues by ctubbsii

Modified:
    accumulo/site/trunk/content/release_notes/1.7.0.mdtext

Modified: accumulo/site/trunk/content/release_notes/1.7.0.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.7.0.mdtext?rev=1680399&r1=1680398&r2=1680399&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.7.0.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.7.0.mdtext Tue May 19 21:45:17 2015
@@ -268,6 +268,34 @@ to reduce the quantity of sockets we nee
 non-cached connection for the message requesting loads of metadata tablets,
 we can ensure that this deadlock won't occur.
 
+## Other changes
+
+### VERSIONS file present in binary distribution
+
+In the pre-built binary distribution, or distributions built by users from the
+official source release, users will now see a `VERSIONS` file present in the lib
+directory alongside the Accumulo server-side jars. Because the created tarball
+strips off versions from the jar file names, it can be extra work to actually
+find what the version of the deployed jars is.
+
+[ACCUMULO-2863][ACCUMULO-2863] adds this `VERSIONS` file to the `lib/` directory
+which contains the Maven groupId, artifactId, and verison (GAV) information for
+each jar file.
+
+### Per-Table Volume Chooser
+
+The `VolumeChooser` interface is a server-side extension point that allows user
+tables to provide custom logic in choosing where its files are written when multiple
+HDFS instances are available. By default, a randomized volume chooser implementation
+is used to evenly balance files across all HDFS instances.
+
+Previously, this VolumeChooser logic was instance-wide which meant that it would
+affect system tables. This is potentially undesirable as it might unintentionally
+impact other users in a multi-tenant system. [ACCUMULO-3177][ACCUMULO-3177] introduces
+a new per-table property which supports configuration of a `VolumeChooser`. This
+ensures that the implementation to choose how HDFS utilization happens when multiple
+are available is limited to the expected subset of all tables.
+
 ## Testing
 
 Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run 
@@ -343,8 +371,10 @@ and, in HDFS High-Availability instances
 [ACCUMULO-1950]: https://issues.apache.org/jira/browse/ACCUMULO-1950
 [ACCUMULO-1957]: https://issues.apache.org/jira/browse/ACCUMULO-1957
 [ACCUMULO-2815]: https://issues.apache.org/jira/browse/ACCUMULO-2815
+[ACCUMULO-2863]: https://issues.apache.org/jira/browse/ACCUMULO-2863
 [ACCUMULO-2998]: https://issues.apache.org/jira/browse/ACCUMULO-2998
 [ACCUMULO-3134]: https://issues.apache.org/jira/browse/ACCUMULO-3134
+[ACCUMULO-3177]: https://issues.apache.org/jira/browse/ACCUMULO-3177
 [ACCUMULO-3439]: https://issues.apache.org/jira/browse/ACCUMULO-3439
 [ACCUMULO-3597]: https://issues.apache.org/jira/browse/ACCUMULO-3597
 [ACCUMULO-3657]: https://issues.apache.org/jira/browse/ACCUMULO-3657