Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-6264 Typos in the book documentation 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1379212 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2012-08-30 23:09:43 +00:00
parent 9959725df4
commit 39f18398e9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/docbkx/book.xml
View File

@ -831,7 +831,7 @@ System.out.println("md5 digest as string length: " + sbDigest.length); // ret
Secondary Indexes and Alternate Query Paths Secondary Indexes and Alternate Query Paths
</title> </title>
<para>This section could also be titled "what if my table rowkey looks like <emphasis>this</emphasis> but I also want to query my table like <emphasis>that</emphasis>." <para>This section could also be titled "what if my table rowkey looks like <emphasis>this</emphasis> but I also want to query my table like <emphasis>that</emphasis>."
A common example on the dist-list is where a row-key is of the format "user-timestamp" but there are are reporting requirements on activity across users for certain A common example on the dist-list is where a row-key is of the format "user-timestamp" but there are reporting requirements on activity across users for certain
time ranges. Thus, selecting by user is easy because it is in the lead position of the key, but time is not. time ranges. Thus, selecting by user is easy because it is in the lead position of the key, but time is not.
</para> </para>
<para>There is no single answer on the best way to handle this because it depends on... <para>There is no single answer on the best way to handle this because it depends on...
@ -1330,7 +1330,7 @@ if (!b) {
<section xml:id="arch.catalog"> <section xml:id="arch.catalog">
<title>Catalog Tables</title> <title>Catalog Tables</title>
<para>The catalog tables -ROOT- and .META. exist as HBase tables. They are are filtered out <para>The catalog tables -ROOT- and .META. exist as HBase tables. They are filtered out
of the HBase shell's <code>list</code> command, but they are in fact tables just like any other. of the HBase shell's <code>list</code> command, but they are in fact tables just like any other.
</para> </para>
<section xml:id="arch.catalog.root"> <section xml:id="arch.catalog.root">