[
https://issues.apache.org/jira/browse/HBASE-16412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416689#comment-16416689
]
Hudson commented on HBASE-16412:
--------------------------------
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Warnings from asciidoc
> ----------------------
>
> Key: HBASE-16412
> URL: https://issues.apache.org/jira/browse/HBASE-16412
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Nick Dimiduk
> Assignee: stack
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: 0001-HBASE-16412-Warnings-from-asciidoc.patch
>
>
> Notice this building to 1.1.6rc, looks like some illegal syntax.
> {noformat}
> [INFO] --- asciidoctor-maven-plugin:1.5.2.1:process-asciidoc (output-pdf) @
> hbase ---
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for pass
> 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>
> Pass the file to the <code>-d</code> argument of the <code>curl</code>
> request.
> 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>
> Pass the file to the <code>-d</code> argument of the <code>curl</code>
> request.
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_indexterm
> asciidoctor: WARNING: conversion missing in backend pdf for inline_image
> asciidoctor: WARNING: conversion missing in backend pdf for inline_image
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
