Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B07DD9F3B for ; Fri, 31 Aug 2012 03:55:11 +0000 (UTC) Received: (qmail 14320 invoked by uid 500); 31 Aug 2012 03:55:11 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 14185 invoked by uid 500); 31 Aug 2012 03:55:11 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 13996 invoked by uid 99); 31 Aug 2012 03:55:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2012 03:55:10 +0000 Date: Fri, 31 Aug 2012 14:55:10 +1100 (NCT) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: <17943999.20268.1346385310874.JavaMail.jiratomcat@arcas> In-Reply-To: <266159074.48159.1340481703880.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6264) Typos in the book documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6264?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1344= 5611#comment-13445611 ]=20 Hudson commented on HBASE-6264: ------------------------------- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #155 (See [https://builds.apache.= org/job/HBase-TRUNK-on-Hadoop-2.0.0/155/]) HBASE-6264 Typos in the book documentation (Revision 1379212) Result =3D FAILURE stack :=20 Files :=20 * /hbase/trunk/src/docbkx/book.xml =20 > Typos in the book documentation > ------------------------------- > > Key: HBASE-6264 > URL: https://issues.apache.org/jira/browse/HBASE-6264 > Project: HBase > Issue Type: Improvement > Components: documentation > Affects Versions: 0.94.0 > Reporter: Jean-Marc Spaggiari > Priority: Minor > Labels: documentation > Fix For: 0.96.0 > > Attachments: typo_HBASE_6264.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > In section 6.9: http://hbase.apache.org/book/secondary.indexes.html > In section 9.2: http://hbase.apache.org/book/arch.catalog.html > There is "are are" twice. I'm not 100% sure what's the best way to propos= e a fix, so I have included the patch below. If that's fine, I will probabl= y propose some other corrections. > JM > Index: branches/0.94/src/docbkx/book.xml > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- branches/0.94/src/docbkx/book.xml=09(r=C3=A9vision 1352979) > +++ branches/0.94/src/docbkx/book.xml=09(copie de travail) > @@ -828,7 +828,7 @@ > 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 acros= s users for certain=20 > + 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 us= ers for certain=20 > time ranges. Thus, selecting by user is easy because it is in the lea= d position of the key, but time is not. > > There is no single answer on the best way to handle this because= it depends on... > @@ -1324,7 +1324,7 @@ > =20 > =09
> =09 Catalog Tables > -=09 The catalog tables -ROOT- and .META. exist as HBase tables. = They are are filtered out=20 > +=09 The catalog tables -ROOT- and .META. exist as HBase tables. = They are filtered out=20 > =09 of the HBase shell's list command, but they are in fac= t tables just like any other. > > =09
-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira