accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1586656 - in /accumulo/site/branches/redesign14/content: bylaws.mdtext notable_features.mdtext
Date Fri, 11 Apr 2014 13:54:15 GMT
Author: bhavanki
Date: Fri Apr 11 13:54:15 2014
New Revision: 1586656

Fix bylaw tables; use labels for noting new feature versions.


Modified: accumulo/site/branches/redesign14/content/bylaws.mdtext
--- accumulo/site/branches/redesign14/content/bylaws.mdtext (original)
+++ accumulo/site/branches/redesign14/content/bylaws.mdtext Fri Apr 11 13:54:15 2014
@@ -111,7 +111,7 @@ Within the Accumulo project, different t
 Decisions regarding the project are made by votes on the primary project development mailing
list: Where necessary, PMC voting may take place on the private Accumulo
PMC mailing list: Votes are clearly indicated by a subject line
starting with [VOTE]. A vote message may only pertain to a single item’s approval; multiple
items should be separated into multiple messages. Voting is carried out by replying to the
vote mail. A vote may take on one of four forms, defined below.
+<table class="table">
@@ -132,7 +132,7 @@ Voting can also be applied to changes to
 These are the types of approvals that can be sought. Different actions require different
types of approvals.
+<table class="table">
 <tr><th>Approval Type</th>
 <tr><td>Consensus Approval</td>
@@ -153,7 +153,7 @@ 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.
+<table class="table">

Modified: accumulo/site/branches/redesign14/content/notable_features.mdtext
--- accumulo/site/branches/redesign14/content/notable_features.mdtext (original)
+++ accumulo/site/branches/redesign14/content/notable_features.mdtext Fri Apr 11 13:54:15
@@ -95,7 +95,7 @@ to adjust the timestamps they issue. So 
 always correct and master authoritative time tries to ensure that timestamps
 are meaningful.
-### Logical Time for bulk import (1.4)
+### Logical Time for bulk import <span class="label label-default">1.4</span>
 Logical time as described above works with streaming (batch) ingest, where the
 tablet server assigns the timestamp.  Logical time is also important for bulk
@@ -109,7 +109,7 @@ file is imported, but whenever it is rea
 time is obtained and always used by the specialized system iterator to set that
-### FATE (1.4)
+### FATE <span class="label label-default">1.4</span>
 Fault Tolerant Executor. A framework for executing operations in a fault
 tolerant manner. In the previous release, if the master process died in the
@@ -161,7 +161,7 @@ does not activate for short scans.
 Recently scanned data is cached into memory.  There are separate caches for
 indexes and data.  Caching can be turned on and off for individual tables.
-### Multi-level RFile Index (1.4)
+### Multi-level RFile Index <span class="label label-default">1.4</span>
 RFiles store an index of the last key in each block. For large files the index
 can become quite large. When the index is large a lot of memory is consumed and
@@ -172,7 +172,7 @@ written. When an index block exceeds the
 written out between data blocks. The size of index blocks is configurable on a
 per table basis.
-### Binary search in RFile blocks (1.5)
+### Binary search in RFile blocks <span class="label label-default">1.5</span>
 RFile uses its index to locate a block of key values.  Once it reaches a block 
 it performs a linear scan to find a key on interest.  Starting with 1.5, Accumulo
@@ -189,7 +189,7 @@ to read patterns without precomputing bl
 The Accumulo client API has a mock implementation that is useful writing unit
 test against Accumulo. Mock Accumulo is in memory and in process.
-### Mini Accumulo Cluster (1.5 & 1.4.4)
+### Mini Accumulo Cluster <span class="label label-default">1.5</span> <span
class="label label-default">1.4.4</span>
 Mini Accumulo cluster is a set of utility code that makes it easy to spin up 
 a local Accumulo instance running against the local filesystem.  Mini Accumulo
@@ -255,7 +255,7 @@ could be different from the Accumulo nod
 Accumulo can be a source and/or sink for map reduce jobs.
-### Thrift Proxy (1.5 & 1.4.4)
+### Thrift Proxy <span class="label label-default">1.5</span> <span class="label
 The Accumulo client code contains a lot of complexity.  For example, the 
 client code locates tablets, retries in the case of failures, and supports 
@@ -343,7 +343,7 @@ multiplied by the largest file size.  If
 files, the largest file is removed from consideration, and the remaining files
 are considered for compaction.  This is done until there are no files to merge.
-### Merging Minor Compaction (1.4)
+### Merging Minor Compaction <span class="label label-default">1.4</span>
 When a max number of files per tablet is reached, minor compactions will merge
 data from the in-memory map with the smallest file instead of creating new
@@ -353,7 +353,7 @@ was growing.  Without this feature, inge
 constant rate, even as scan performance decreases because tablets have too many
-### Loading jars using VFS (1.5)
+### Loading jars using VFS <span class="label label-default">1.5</span>
 User written iterators are a useful way to manipulate data in data in Accumulo. 
 Before 1.5., users had to copy their iterators to each tablet server.  Starting 
@@ -376,13 +376,13 @@ Arbitrary split points can be added to a
 This is useful for increasing ingest performance on a new table. It can also be
 used to accommodate new data patterns in an existing table.
-### Tablet Merging (1.4)
+### Tablet Merging <span class="label label-default">1.4</span>
 Tablet merging is a new feature. Merging of tablets can be requested in the
 shell; Accumulo does not merge tablets automatically. In 1.5, the METADATA tablets 
 can be merged.
-### Table Cloning (1.4)
+### Table Cloning <span class="label label-default">1.4</span>
 Allows users to quickly create a new table that references an existing table's
 data and copies its configuration. A cloned table and its source table can be
@@ -390,16 +390,16 @@ mutated independently. Testing was the m
 feature. For example to test a new filtering iterator, clone the table, add the
 filter to the clone, and force a major compaction.
-### Import/Export Table (1.5)
+### Import/Export Table <span class="label label-default">1.5</span>
 An offline tables metadata and files can easily be copied to another cluster and 
-### Compact Range (1.4)
+### Compact Range <span class="label label-default">1.4</span>
 Compact each tablet that falls within a row range down to a single file.  
-### Delete Range (1.4)
+### Delete Range <span class="label label-default">1.4</span>
 Added an operation to efficiently delete a range of rows from a table. Tablets
 that fall completely within a range are simply dropped. Tablets overlapping the

View raw message