[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
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 u123 and use a batch size of 100, the
> filter file would look like this:
> { "type": "PrefixFilter",
> "value": "u123" }
> {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)
[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
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 u123 and use a batch size of 100, the
> filter file would look like this:
> { "type": "PrefixFilter",
> "value": "u123" }
> {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)
[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-18635:
--
Attachment: HBASE-18635.master.002.patch
> 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,
> 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 u123 and use a batch size of 100, the
> filter file would look like this:
> { "type": "PrefixFilter",
> "value": "u123" }
> {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)
[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-18635:
--
Status: Patch Available (was: In Progress)
> 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 u123 and use a batch size of 100, the
> filter file would look like this:
> { "type": "PrefixFilter",
> "value": "u123" }
> {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)
[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-18635:
--
Attachment: HBASE-18635.master.001.patch
> Fix asciidoc warnings
> -
>
> Key: HBASE-18635
> URL: https://issues.apache.org/jira/browse/HBASE-18635
> Project: HBase
> Issue Type: Bug
>Reporter: Misty Stanley-Jones
> 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 u123 and use a batch size of 100, the
> filter file would look like this:
> { "type": "PrefixFilter",
> "value": "u123" }
> {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)
