[
https://issues.apache.org/jira/browse/NIFI-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429425#comment-15429425
]
ASF GitHub Bot commented on NIFI-1971:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/858
@pvillard31
The error is expected as the regex does not contain a capture group named
KEY. It is a bug as I should detect KEY or whatever value was chosen.
But your feedback highlights that instead of having named captures on regex
vs numbered captures on split, we rather have a single approach (i.e. numbered
captures) across both parsing strategies.
I will fix it and also provide some better insight via validation messages
> Create a batch capable pseudo-whois ("netcat") enrichment Processor
> -------------------------------------------------------------------
>
> Key: NIFI-1971
> URL: https://issues.apache.org/jira/browse/NIFI-1971
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.0.0, 0.7.0
> Reporter: Andre
> Assignee: Andre
> Fix For: 1.1.0
>
>
> While the QueryDNS created can be used on low to medium volume enrichment and
> to licensed DNS based lookups (e.g. commercial use of SpamHaus) many
> enrichment providers prefer the use of bulk queries using pseudo whois API
> (a.k.a. netcat interface).
> as documented
> [here|https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc6] the
> bulk interfaces work by connecting to port 43/TCP and sending a payload like:
> {code}
> begin origin
> 4.5.4.3
> 17.112.152.32
> 208.77.188.166
> end
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
