Author: jamestaylor
Date: Fri Mar 11 05:43:22 2016
New Revision: 1734495
URL: http://svn.apache.org/viewvc?rev=1734495&view=rev
Log:
Update label of secondary index page
Modified:
phoenix/site/publish/secondary_indexing.html
phoenix/site/source/src/site/markdown/secondary_indexing.md
Modified: phoenix/site/publish/secondary_indexing.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/secondary_indexing.html?rev=1734495&r1=1734494&r2=1734495&view=diff
==============================================================================
--- phoenix/site/publish/secondary_indexing.html (original)
+++ phoenix/site/publish/secondary_indexing.html Fri Mar 11 05:43:22 2016
@@ -243,7 +243,7 @@ CREATE LOCAL INDEX my_index ON my_table
<p>Note that if the primary table is salted, then the index is automatically
salted in the same way for global indexes. In addition, the MAX_FILESIZE for
the index is adjusted down, relative to the size of the primary versus index
table. For more on salting see <a href="salted.html">here</a>. With local
indexes, on the other hand, specifying SALT_BUCKETS is not allowed.</p>
</div>
<div class="section">
- <h2 id="Consistency_Guarantees">Consistency Guarantees</h2>
+ <h2 id="Consistency"> Consistency Guarantees<a
name="Consistency_Guarantees"></a></h2>
<p>On successful return to the client after a commit, all data is guaranteed
to be written to all interested indexes and the primary table. In other words,
index updates are synchronous with the same strong consistency guarantees
provided by HBase.</p>
<p>However, since indexes are stored in separate tables than the data table,
depending on the properties of the table and the type of index, the consistency
between your table and index varies in the event that a commit fails due to a
server-side crash. This is an important design consideration driven by your
requirements and use case.</p>
<p>Outlined below are the different options with various levels of
consistency guarantees.</p>
Modified: phoenix/site/source/src/site/markdown/secondary_indexing.md
URL:
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/secondary_indexing.md?rev=1734495&r1=1734494&r2=1734495&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/secondary_indexing.md (original)
+++ phoenix/site/source/src/site/markdown/secondary_indexing.md Fri Mar 11
05:43:22 2016
@@ -92,7 +92,7 @@ Just like with the <code>CREATE TABLE</c
SALT_BUCKETS=10, DATA_BLOCK_ENCODING='NONE'
Note that if the primary table is salted, then the index is automatically
salted in the same way for global indexes. In addition, the MAX_FILESIZE for
the index is adjusted down, relative to the size of the primary versus index
table. For more on salting see [here](salted.html). With local indexes, on the
other hand, specifying SALT_BUCKETS is not allowed.
-## Consistency Guarantees
+##<a id="Consistency"/> Consistency Guarantees
On successful return to the client after a commit, all data is guaranteed to
be written to all interested indexes and the
primary table. In other words, index updates are synchronous with the same
strong consistency guarantees provided by HBase.
