svn commit: r1592779 - /accumulo/site/trunk/content/release_notes/1.6.0.mdtext

[kt...@apache.org]

Author: kturner
Date: Tue May  6 15:28:29 2014
New Revision: 1592779

URL: http://svn.apache.org/r1592779
Log:
ACCUMULO-2396 remove draft and clean up some errors

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

Modified: accumulo/site/trunk/content/release_notes/1.6.0.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.6.0.mdtext?rev=1592779&r1=1592778&r2=1592779&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.6.0.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.6.0.mdtext Tue May  6 15:28:29 2014
@@ -16,8 +16,6 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-**DRAFT 1.6.0 RELEASE NOTES**
-
 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.  
 
 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.
@@ -48,11 +46,11 @@ The only built in test that conditional 
 
 Encryption is still an experimental feature, but much progress has been made since 1.5.0.  Support for encrypting rfiles and write ahead logs were added in [ACCUMULO-958][ACCUMULO-958] and [ACCUMULO-980][ACCUMULO-980].  Support for encrypting data over the wire using SSL was added in [ACCUMULO-1009][ACCUMULO-1009].
  
-When a tablet server fails, its write ahead logs are sorted and stored in HDFS.  In 1.6.0, encrypting these sorted write ahead logs is not supported.  [ACCUMULO-981][ACCUMULO-981] addresses this issue.  
+When a tablet server fails, its write ahead logs are sorted and stored in HDFS.  In 1.6.0, encrypting these sorted write ahead logs is not supported.  [ACCUMULO-981][ACCUMULO-981] is open to address this issue.  
 
 ### Pluggable compaction strategies
 
-One of the key elements of the [BigTable][1] design is use of the [Log Structured Merge Tree][2].  This entails sorting data in memory, writing out sorted files, and then later merging multiple sorted files into a single file.   These automatic merges happen in the background and Accumulo decides when to merge files based comparing relative sizes of files to a compaction ratio.  Adjusting the compaction ratio is the only way a user can control this process.  [ACCUMULO-1451][ACCUMULO-1451] introduces pluggable compaction strategies which allow users to choose when and what files to compact.  [ACCUMULO-1808][ACCUMULO-1808] adds a compaction strategy the prevents compaction of files over a configurable size.
+One of the key elements of the [BigTable][1] design is use of the [Log Structured Merge Tree][2].  This entails sorting data in memory, writing out sorted files, and then later merging multiple sorted files into a single file.   These automatic merges happen in the background and Accumulo decides when to merge files based comparing relative sizes of files to a compaction ratio.  Before 1.6.0 adjusting the compaction ratio was the only way a user could control this process.  [ACCUMULO-1451][ACCUMULO-1451] introduces pluggable compaction strategies which allow users to choose when and what files to compact.  [ACCUMULO-1808][ACCUMULO-1808] adds a compaction strategy that prevents compaction of files over a configurable size.
 
 ### Lexicoders
 
@@ -73,7 +71,7 @@ In cases where a very small amount of da
 
 ### Service IP addresses
 
-Previous versions of Accumulo always used IP addresses internally.  This could be problematic in virtual machine environments where IP addresses change.  In [ACCUMULO-1585][ACCUMULO-1585] this was changed, now the accumulo uses the exact hostnames from its config files for internal addressing.  
+Previous versions of Accumulo always used IP addresses internally.  This could be problematic in virtual machine environments where IP addresses change.  In [ACCUMULO-1585][ACCUMULO-1585] this was changed, now Accumulo uses the exact hostnames from its config files for internal addressing.  
 
 All Accumulo processes running on a cluster are locatable via zookeeper.  Therefore using well known ports is not really required.  [ACCUMULO-1664][ACCUMULO-1664] makes it possible to for all Accumulo processes to use random ports.  This makes it easier to run multiple Accumulo instances on a single node.