hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Misty Stanley-Jones (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18635) Fix asciidoc warnings
Date Sat, 19 Aug 2017 17:39:00 GMT
Misty Stanley-Jones created HBASE-18635:
-------------------------------------------

             Summary: Fix asciidoc warnings
                 Key: HBASE-18635
                 URL: https://issues.apache.org/jira/browse/HBASE-18635
             Project: HBase
          Issue Type: Bug
            Reporter: Misty Stanley-Jones


When building docs, I noticed:

{code}
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 &lt;codeph&gt;u123&lt;/codeph&gt;
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>

{code}

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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message