[HBASE-18635] Fix asciidoc warnings

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Hadoop Flags: Reviewed
• Assignee: Jan Hentschel
• Reporter: M Linville
• Created: 19/Aug/17 17:38
• Updated: 01/Aug/18 06:21
• Resolved: 28/Aug/17 03:19

Description

When building docs, I noticed:

Failed to parse formatted text: To supply filters to the Scanner object or configure the Scanner in any other way, you can create a text file and add your filter to the file. For example, to return only rows for which keys start with <codeph>u123</codeph> and use a batch size of 100, the filter file would look like this:

 <pre> &lt;Scanner batch="100"&gt; &lt;filter&gt; { "type": "PrefixFilter", "value": "u123" } &lt;/filter&gt; &lt;/Scanner&gt; </pre>

Working hypthesis is that we should either be using proper codeblocks rather than pre tags. Otherwise we may need to do something to escape curly braces. Asciidoctor is probably trying to interpret them as Liquid tags.

Issue Links

• relates to: HBASE-15041 Clean up javadoc errors and reenable jdk8 linter
• links to: Review Board (master)