[
https://issues.apache.org/jira/browse/NIFI-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Erkamaa updated NIFI-13667:
-----------------------------------
Description: Would It be possible to make an ISPEnrichIPRecord you already
have an ISPEnrichIP processor and a GeoEnrichIP and a GeoEnrichIPRecord
processor. It would be really nice to have an ISPEnrichIPRecord that behaves
like the existing GeoEnrichIPRecord because you can have much more throughput
with these record processors and don't need to deal with extracting and
attribute and using that to do the search like in ISPEnrichIP and GeoEnrichIP.
I would hope this is not too much work to implement and you can already use
most of the code you have for GeoEnrichIPRecord. This new ISPEnrichIPRecord
processor would have a path for the maxmind DB, record reader, record writer, a
required field for the IP to look up, and optional feilds for the enrichment
information to be written to the record just like the GeoEnrichIPRecord
processor. (was: Would It be possible to make an ISPEnrichIPRecord you
already have an ISPEnrichIP processor and a GeoEnrichIP and a GeoEnrichIPRecord
processor. It would be really nice to have an ISPEnrichIPRecord that behaves
like the existing GeoEnrichIPRecord because you can have much more throughput
with these record processors and don't need to deal with extracting and
attribute and using that to do the search like in ISPEnrichIP and GeoEnrichIP.
I would hope this is not too much work to implement and you can already use
most of the code you have for GeoEnrichIPRecord. )
> ISPEnrichIPRecord Processor
> ---------------------------
>
> Key: NIFI-13667
> URL: https://issues.apache.org/jira/browse/NIFI-13667
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Brandon Erkamaa
> Priority: Major
>
> Would It be possible to make an ISPEnrichIPRecord you already have an
> ISPEnrichIP processor and a GeoEnrichIP and a GeoEnrichIPRecord processor. It
> would be really nice to have an ISPEnrichIPRecord that behaves like the
> existing GeoEnrichIPRecord because you can have much more throughput with
> these record processors and don't need to deal with extracting and attribute
> and using that to do the search like in ISPEnrichIP and GeoEnrichIP. I would
> hope this is not too much work to implement and you can already use most of
> the code you have for GeoEnrichIPRecord. This new ISPEnrichIPRecord processor
> would have a path for the maxmind DB, record reader, record writer, a
> required field for the IP to look up, and optional feilds for the enrichment
> information to be written to the record just like the GeoEnrichIPRecord
> processor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
