hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Misty Stanley-Jones (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18635) Fix asciidoc warnings
Date Mon, 28 Aug 2017 03:20:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Misty Stanley-Jones updated HBASE-18635:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

> Fix asciidoc warnings
> ---------------------
>                 Key: HBASE-18635
>                 URL: https://issues.apache.org/jira/browse/HBASE-18635
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Misty Stanley-Jones
>            Assignee: Jan Hentschel
>             Fix For: 3.0.0
>         Attachments: HBASE-18635.master.001.patch, HBASE-18635.master.002.patch
> 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

View raw message