[ https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-18635: -------------------------- Fix Version/s: (was: 3.0.0) 2.0.0 > 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 > Priority: Major > Fix For: 2.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 <codeph>u123</codeph> and use a batch size of 100, the > filter file would look like this: > <pre> <Scanner batch="100"> <filter> { "type": "PrefixFilter", > "value": "u123" } </filter> </Scanner> </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 (v7.6.3#76005)