[2/5] kudu git commit: design docs: Fix bad markdown formatting in tablet.md

[to...@apache.org]

design docs: Fix bad markdown formatting in tablet.md

Level 1 headings are only allowed to have a line of equals signs under
the text of the heading, not before.

Change-Id: I336b7a5814da30812e5dd77289027ac296fcd2da
Reviewed-on: http://gerrit.cloudera.org:8080/6500
Tested-by: Kudu Jenkins
Reviewed-by: Will Berkeley <wd...@gmail.com>


Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/6e74cefd
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/6e74cefd
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/6e74cefd

Branch: refs/heads/master
Commit: 6e74cefda7ce8e325ae4275ae3a7f2eb801a862f
Parents: 023629a
Author: Mike Percy <mp...@apache.org>
Authored: Tue Mar 28 12:24:58 2017 -0700
Committer: Mike Percy <mp...@apache.org>
Committed: Wed Mar 29 21:26:35 2017 +0000

----------------------------------------------------------------------
 docs/design-docs/tablet.md | 13 -------------
 1 file changed, 13 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kudu/blob/6e74cefd/docs/design-docs/tablet.md
----------------------------------------------------------------------
diff --git a/docs/design-docs/tablet.md b/docs/design-docs/tablet.md
index 18a4f2f..b021d10 100644
--- a/docs/design-docs/tablet.md
+++ b/docs/design-docs/tablet.md
@@ -23,7 +23,6 @@ are disjoint, ie the set of rows for different RowSets do not
 intersect, so any given key is present in at most one RowSet. While
 RowSets are disjoint, their key spaces may overlap.
 
-============================================================
 Handling Insertions
 ============================================================
 
@@ -42,7 +41,6 @@ of a special header, followed by the packed format of the row data (more detail
 Since the MemRowSet is fully in-memory, it will eventually fill up and "Flush" to disk --
 this process is described in detail later in this document.
 
-============================================================
 MVCC Overview
 ============================================================
 
@@ -84,7 +82,6 @@ a retention period beyond which old transaction records may be GCed (thus preven
 reads from earlier than that point in history).
 (NOTE: history GC not currently implemented)
 
-============================================================
 MVCC Mutations in MemRowSet
 ============================================================
 
@@ -182,7 +179,6 @@ However, we consider the above inefficiencies tolerable given the following assu
 If it turns out that the above inefficiencies impact real applications, various optimizations
 can be applied in the future to reduce the overhead.
 
-============================================================
 MemRowSet Flushes
 ============================================================
 
@@ -218,7 +214,6 @@ NOTE: other systems such as C-Store call the MemRowSet the
 "write optimized store" (WOS), and the on-disk files the "read-optimized store"
 (ROS).
 
-============================================================
 Historical MVCC in DiskRowSets
 ============================================================
 
@@ -295,7 +290,6 @@ the range of transactions for which UNDO records are present. If the scanner's M
 snapshot indicates that all of these transactions are already committed, then the set
 of deltas may be short circuited, and the query can proceed with no MVCC overhead.
 
-============================================================
 Handling mutations against on-disk files
 ============================================================
 
@@ -341,7 +335,6 @@ This allows for fast updates of small columns without the overhead of reading
 or re-writing larger columns (an advantage compared to the MVCC techniques used
 by systems such as C-Store and PostgreSQL).
 
-============================================================
 Summary of delta file processing
 ============================================================
 
@@ -361,7 +354,6 @@ REDO records: data which needs to be processed in order to bring rows up to date
 
 UNDO records and REDO records are stored in the same file format, called a DeltaFile.
 
-============================================================
 Delta Compactions
 ============================================================
 
@@ -408,7 +400,6 @@ UNDO logs have been removed, there is no remaining record of when any row or
 cell was inserted or updated. If users need this functionality, they should
 keep their own "inserted_on" timestamp column, as they would in a traditional RDBMS.
 
-============================================================
 Types of Delta Compaction
 ============================================================
 
@@ -477,7 +468,6 @@ compaction file can be introduced into the RowSet by atomically swapping it with
 the compaction inputs. After the swap is complete, the pre-compaction files may
 be removed.
 
-============================================================
 Merging compactions
 ============================================================
 
@@ -528,7 +518,6 @@ in a Merging Compaction. This makes the handling of concurrent mutations a somew
 intricate dance. This process is described in more detail in 'compaction.txt' in this
 directory.
 
-============================================================
 Overall picture
 ============================================================
 
@@ -585,7 +574,6 @@ DiskRowSet 2:
 +-----------------+ /
 ```
 
-============================================================
 Comparison to BigTable approach
 ============================================================
 
@@ -690,7 +678,6 @@ not another dimension in the row key. Instead, Kudu provides native composite ro
 which can be useful for time series.
 
 
-============================================================
 Comparing the MVCC implementation to other databases
 ============================================================