[jira] [Resolved] (HBASE-16412) Warnings from asciidoc

["stack (JIRA)" <ji...@apache.org>]

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

stack resolved HBASE-16412.
---------------------------
    Resolution: Fixed

Resolving. Pushed to master.

> 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>
> &lt;Scanner batch="100"&gt;
>   &lt;filter&gt;
>     {
>       "type": "PrefixFilter",
>       "value": "u123"
>     }
>   &lt;/filter&gt;
> &lt;/Scanner&gt;
> </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 &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>
> 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)