[
https://issues.apache.org/jira/browse/HBASE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996642#comment-13996642
]
Jonathan Hsieh commented on HBASE-11155:
----------------------------------------
Thus far these changes look good modulo the nit below.
What command are you running to get the warnings and where the build is broken?
One of our precommit tests checks the doc compile.
Nit: this looks like it snuck in from another patch.
{code}
</section>
<section xml:id="reverse.timestamp"><title>Reverse Timestamps</title>
+ <note>
+ <title>Reverse Scan API</title>
+ <para>
+ <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-4811";>HBASE-4811</link>
implements an API to scan a table or a range within a table in reverse,
reducing the need to optimize your schema for forward or reverse scanning. This
feature is available in HBase 0.98 and later. See <link
xlink:href="https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html#setReversed%28boolean";
/> for more information.
+ </para>
+ </note>
+
{code}
We generally like to have one patch, one jira, one commit. How many more of
these are coming?
If the bunch will be strung out over for more than a few days, I'd rather get
the nit fixed and commit. I would rename the jira to "Fix validation errors in
ref guide (book,configuration,schema_design)" and let you open new issue for
the rest. If you can get them all in the next few days, we can wait for all of
them.
> Fix Validation Errors in Ref Guide
> ----------------------------------
>
> Key: HBASE-11155
> URL: https://issues.apache.org/jira/browse/HBASE-11155
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.98.2
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Attachments: HBASE-11155-book.xml.patch,
> HBASE-11155-configuration.xml.patch, HBASE-11155-schema_design.xml.patch
>
>
> Before I do serious documentation work, I have to fix all of the validation
> errors that are somehow not causing the Ref Guide to break the builds. I will
> attach one patch per file -- that's the easiest way I know how to do it. I
> will try not to make any content changes, only validation changes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
