From 39f18398e9cf5cc195927e252ee651d239a41439 Mon Sep 17 00:00:00 2001 From: Michael Stack Date: Thu, 30 Aug 2012 23:09:43 +0000 Subject: [PATCH] HBASE-6264 Typos in the book documentation git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1379212 13f79535-47bb-0310-9956-ffa450edef68 --- src/docbkx/book.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml index e657274884e..cb4f6480b79 100644 --- a/src/docbkx/book.xml +++ b/src/docbkx/book.xml @@ -831,7 +831,7 @@ System.out.println("md5 digest as string length: " + sbDigest.length); // ret Secondary Indexes and Alternate Query Paths This section could also be titled "what if my table rowkey looks like this but I also want to query my table like that." - 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. There is no single answer on the best way to handle this because it depends on... @@ -1330,7 +1330,7 @@ if (!b) {
Catalog Tables - The catalog tables -ROOT- and .META. exist as HBase tables. They are are filtered out + The catalog tables -ROOT- and .META. exist as HBase tables. They are filtered out of the HBase shell's list command, but they are in fact tables just like any other.