[jira] [Commented] (HBASE-18635) Fix asciidoc warnings

[Hadoop QA (JIRA)]

    [ 
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135206#comment-16135206
 ] 

Hadoop QA commented on HBASE-18635:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
18s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
 3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
 0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
34m 28s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}148m 
42s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
20s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}201m 16s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18635 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12882797/HBASE-18635.master.001.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  |
| uname | Linux e6a6d3c3d6b1 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 820ee91 |
| Default Java | 1.8.0_144 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/8193/testReport/ |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/8193/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>         Attachments: HBASE-18635.master.001.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> &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)