--- results/org.apache.nifi/nifi/2.0.0-M4/oss-rebuild-improved-2/reference/nifi-enrich-nar-2.0.0-M4-nar-extension-manifest.xml:extension-manifest.xml 2025-04-06 12:19:24.074805765 +0000 +++ results/org.apache.nifi/nifi/2.0.0-M4/oss-rebuild-improved-2/rebuild/nifi-enrich-nar-2.0.0-M4-nar-extension-manifest.xml:extension-manifest.xml 2025-04-06 12:19:35.350628669 +0000 @@ -1,3 +1,3 @@ -org.apache.nifinifi-enrich-nar2.0.0-M4org.apache.nifinifi-standard-shared-nar2.0.0-M42.0.0-M4nifi-2.0.0-M4-RC1UNKNOWN19c5be0org.apache.nifi.processors.GeoEnrichIPPROCESSORLooks up geolocation information for an IP address and adds the geo information to FlowFile attributes. The geo data is provided as a MaxMind database. The attribute that contains the IP address to lookup is provided by the 'IP Address Attribute' property. If the name of the attribute provided is 'X', then the the attributes added by enrichment will take the form X.geo.<fieldName>geoenrichipmaxmindGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEDIRECTORYFILEIP Address AttributeIP Address AttributeThe name of an attribute whose value is a dotted decimal IP address for which enrichment should occurtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseX.geo.lookup.microsThe number of microseconds that the geo lookup tookX.geo.cityThe city identified for the IP addressX.geo.accuracyThe accuracy radius if provided by the database (in Kilometers)X.geo.latitudeThe latitude identified for this IP addressX.geo.longitudeThe longitude identified for this IP addressX.geo.subdivision.NEach subdivision that is identified for this IP address is added with a one-up number appended to the attribute name, starting with 0X.geo.subdivision.isocode.NThe ISO code for the subdivision that is identified by X.geo.subdivision.NX.geo.countryThe country identified for this IP addressX.geo.country.isocodeThe ISO Code for the country identifiedX.geo.postalcodeThe postal code for the country identifiedtruetrueINPUT_REQUIREDorg.apache.nifi.processors.GeoEnrichIPRecordPROCESSORLooks up geolocation information for an IP address and adds the geo information to FlowFile attributes. The geo data is provided as a MaxMind database. This version uses the NiFi Record API to allow large scale enrichment of record-oriented data sets. Each field provided by the MaxMind database can be directed to a field of the user's choosing by providing a record path for that field configuration. geoenrichipmaxmindrecordGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEDIRECTORYFILEgeo-enrich-ip-record-readerRecord ReaderRecord reader service to use for reading the flowfile contents.org.apache.nifi.serialization.RecordReaderFactoryorg.apache.nifinifi-standard-services-api-nar2.0.0-M4truefalsefalseNONEfalsefalsegeo-enrich-ip-record-writerRecord WriterRecord writer service to use for enriching the flowfile contents.org.apache.nifi.serialization.RecordSetWriterFactoryorg.apache.nifinifi-standard-services-api-nar2.0.0-M4truefalsefalseNONEfalsefalsegeo-enrich-ip-split-found-not-foundSeparate Enriched From Not EnrichedSeparate records that have been enriched from ones that have not. Default behavior is to send everything to the found relationship if even one record is enriched.falsetruetruefalsefalsetruefalsefalseNONEfalsefalsegeo-enrich-ip-ip-record-pathIP Address Record PathThe record path to retrieve the IP address for doing the lookup.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-city-record-pathCity Record PathRecord path for putting the city identified for the IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-latitude-record-pathLatitude Record PathRecord path for putting the latitude identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-longitude-record-pathLongitude Record PathRecord path for putting the longitude identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-record-pathCountry Record PathRecord path for putting the country identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-iso-record-pathCountry ISO Code Record PathRecord path for putting the ISO Code for the country identifiedfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-postal-record-pathCountry Postal Code Record PathRecord path for putting the postal code for the country identifiedfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalseoriginalThe original input flowfile goes to this relationship regardless of whether the content was enriched or not.falsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseINPUT_REQUIREDorg.apache.nifi.processors.ISPEnrichIPPROCESSORLooks up ISP information for an IP address and adds the information to FlowFile attributes. The ISP data is provided as a MaxMind ISP database. (Note that this is NOT the same as the GeoLite database utilized by some geo enrichment tools). The attribute that contains the IP address to lookup is provided by the 'IP Address Attribute' property. If the name of the attribute provided is 'X', then the the attributes added by enrichment will take the form X.isp.<fieldName>ISPenrichipmaxmindGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEDIRECTORYFILEIP Address AttributeIP Address AttributeThe name of an attribute whose value is a dotted decimal IP address for which enrichment should occurtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseX.isp.lookup.microsThe number of microseconds that the geo lookup tookX.isp.asnThe Autonomous System Number (ASN) identified for the IP addressX.isp.asn.organizationThe Organization Associated with the ASN identifiedX.isp.nameThe name of the ISP associated with the IP address providedX.isp.organizationThe Organization associated with the IP address providedtruetrueINPUT_REQUIREDorg.apache.nifi.processors.enrich.QueryDNSPROCESSORA powerful DNS query processor primary designed to enrich DataFlows with DNS based APIs (e.g. RBLs, ShadowServer's ASN lookup) but that can be also used to perform regular DNS lookups.dnsenrichipQUERY_INPUTLookup valueThe value that should be used to populate the querytruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseQUERY_PARSERResults ParserThe method used to slice the results into attribute groupsNoneSplitSplitUse a delimiter character or RegEx to split the results into attributesRegExRegExUse a regular expression to split the results into attributes NoneNoneDo not split resultstruefalsefalseNONEfalsefalseQUERY_PARSER_INPUTParser RegExChoice between a splitter and regex matcher used to parse the results of the query into attribute groups. +org.apache.nifinifi-enrich-nar2.0.0-M4org.apache.nifinifi-standard-shared-nar2.0.0-M42.0.0-M4nifi-2.0.0-M4-RC1UNKNOWN19c5be0org.apache.nifi.processors.GeoEnrichIPPROCESSORLooks up geolocation information for an IP address and adds the geo information to FlowFile attributes. The geo data is provided as a MaxMind database. The attribute that contains the IP address to lookup is provided by the 'IP Address Attribute' property. If the name of the attribute provided is 'X', then the the attributes added by enrichment will take the form X.geo.<fieldName>geoenrichipmaxmindGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEFILEDIRECTORYIP Address AttributeIP Address AttributeThe name of an attribute whose value is a dotted decimal IP address for which enrichment should occurtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseX.geo.lookup.microsThe number of microseconds that the geo lookup tookX.geo.cityThe city identified for the IP addressX.geo.accuracyThe accuracy radius if provided by the database (in Kilometers)X.geo.latitudeThe latitude identified for this IP addressX.geo.longitudeThe longitude identified for this IP addressX.geo.subdivision.NEach subdivision that is identified for this IP address is added with a one-up number appended to the attribute name, starting with 0X.geo.subdivision.isocode.NThe ISO code for the subdivision that is identified by X.geo.subdivision.NX.geo.countryThe country identified for this IP addressX.geo.country.isocodeThe ISO Code for the country identifiedX.geo.postalcodeThe postal code for the country identifiedtruetrueINPUT_REQUIREDorg.apache.nifi.processors.GeoEnrichIPRecordPROCESSORLooks up geolocation information for an IP address and adds the geo information to FlowFile attributes. The geo data is provided as a MaxMind database. This version uses the NiFi Record API to allow large scale enrichment of record-oriented data sets. Each field provided by the MaxMind database can be directed to a field of the user's choosing by providing a record path for that field configuration. geoenrichipmaxmindrecordGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEFILEDIRECTORYgeo-enrich-ip-record-readerRecord ReaderRecord reader service to use for reading the flowfile contents.org.apache.nifi.serialization.RecordReaderFactoryorg.apache.nifinifi-standard-services-api-nar2.0.0-M4truefalsefalseNONEfalsefalsegeo-enrich-ip-record-writerRecord WriterRecord writer service to use for enriching the flowfile contents.org.apache.nifi.serialization.RecordSetWriterFactoryorg.apache.nifinifi-standard-services-api-nar2.0.0-M4truefalsefalseNONEfalsefalsegeo-enrich-ip-split-found-not-foundSeparate Enriched From Not EnrichedSeparate records that have been enriched from ones that have not. Default behavior is to send everything to the found relationship if even one record is enriched.falsetruetruefalsefalsetruefalsefalseNONEfalsefalsegeo-enrich-ip-ip-record-pathIP Address Record PathThe record path to retrieve the IP address for doing the lookup.truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-city-record-pathCity Record PathRecord path for putting the city identified for the IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-latitude-record-pathLatitude Record PathRecord path for putting the latitude identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-longitude-record-pathLongitude Record PathRecord path for putting the longitude identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-record-pathCountry Record PathRecord path for putting the country identified for this IP addressfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-iso-record-pathCountry ISO Code Record PathRecord path for putting the ISO Code for the country identifiedfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalsegeo-enrich-ip-country-postal-record-pathCountry Postal Code Record PathRecord path for putting the postal code for the country identifiedfalsefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalseoriginalThe original input flowfile goes to this relationship regardless of whether the content was enriched or not.falsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseINPUT_REQUIREDorg.apache.nifi.processors.ISPEnrichIPPROCESSORLooks up ISP information for an IP address and adds the information to FlowFile attributes. The ISP data is provided as a MaxMind ISP database. (Note that this is NOT the same as the GeoLite database utilized by some geo enrichment tools). The attribute that contains the IP address to lookup is provided by the 'IP Address Attribute' property. If the name of the attribute provided is 'X', then the the attributes added by enrichment will take the form X.isp.<fieldName>ISPenrichipmaxmindGeo Database FileMaxMind Database FilePath to Maxmind IP Enrichment Database FiletruefalsetrueENVIRONMENTfalsefalseSINGLEFILEDIRECTORYIP Address AttributeIP Address AttributeThe name of an attribute whose value is a dotted decimal IP address for which enrichment should occurtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseLog LevelLog LevelThe Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.WARNtruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsenot foundWhere to route flow files after unsuccessfully enriching attributes because no data was foundfalsefoundWhere to route flow files after successfully enriching attributes with data provided by databasefalseX.isp.lookup.microsThe number of microseconds that the geo lookup tookX.isp.asnThe Autonomous System Number (ASN) identified for the IP addressX.isp.asn.organizationThe Organization Associated with the ASN identifiedX.isp.nameThe name of the ISP associated with the IP address providedX.isp.organizationThe Organization associated with the IP address providedtruetrueINPUT_REQUIREDorg.apache.nifi.processors.enrich.QueryDNSPROCESSORA powerful DNS query processor primary designed to enrich DataFlows with DNS based APIs (e.g. RBLs, ShadowServer's ASN lookup) but that can be also used to perform regular DNS lookups.dnsenrichipQUERY_INPUTLookup valueThe value that should be used to populate the querytruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseQUERY_PARSERResults ParserThe method used to slice the results into attribute groupsNoneSplitSplitUse a delimiter character or RegEx to split the results into attributesRegExRegExUse a regular expression to split the results into attributes NoneNoneDo not split resultstruefalsefalseNONEfalsefalseQUERY_PARSER_INPUTParser RegExChoice between a splitter and regex matcher used to parse the results of the query into attribute groups. NOTE: This is a multiline regular expression, therefore, the DFM should decide how to handle trailing new line characters.falsefalsefalseNONEfalsefalseDNS_RETRIESDNS Query RetriesThe number of attempts before giving up and moving on1truefalsefalseNONEfalsefalseDNS_TIMEOUTDNS Query TimeoutThe amount of time to wait until considering a query as failed1500 mstruefalsefalseNONEfalsefalseDNS_SERVERDNS ServersA comma separated list of DNS servers to be used. (Defaults to system wide if none is used)falsefalsefalseNONEfalsefalseDNS_QUERY_TYPEDNS Query TypeThe DNS query type to be used by the processor (e.g. TXT, A)TXTtruefalsefalseNONEfalsefalsenot foundWhere to route flow files if data enrichment query rendered no resultsfalsefoundWhere to route flow files after successfully enriching attributes with datafalseenrich.dns.record*.group*The captured fields of the DNS query response for each of the records receivedtruetrueINPUT_REQUIREDorg.apache.nifi.processors.enrich.QueryWhoisPROCESSORA powerful whois query processor primary designed to enrich DataFlows with whois based APIs (e.g. ShadowServer's ASN lookup) but that can be also used to perform regular whois lookups.whoisenrichipQUERY_INPUTLookup valueThe value that should be used to populate the querytruefalsetrueFLOWFILE_ATTRIBUTESfalsefalseWHOIS_QUERY_TYPEWhois Query TypeThe Whois query type to be used by the processor (if used)falsefalsefalseNONEfalsefalseWHOIS_SERVERWhois ServerThe Whois server to be usedtruefalsefalseNONEfalsefalseWHOIS_SERVER_PORTWhois Server PortThe TCP port of the remote Whois server43truefalsefalseNONEfalsefalseWHOIS_TIMEOUTWhois Query TimeoutThe amount of time to wait until considering a query as failed1500 mstruefalsefalseNONEfalsefalseBATCH_SIZEBatch SizeThe number of incoming FlowFiles to process in a single execution of this processor. 25truefalsefalseNONEfalsefalseBULK_PROTOCOLBulk ProtocolThe protocol used to perform the bulk query. NoneBegin/EndBegin/EndThe evaluated input of each flowfile is enclosed within begin and end tags. Each row contains a delimited set of fieldsNoneNoneQueries are made without any particular dialecttruefalsefalseNONEfalsefalseQUERY_PARSERResults ParserThe method used to slice the results into attribute groupsNoneSplitSplitUse a delimiter character or RegEx to split the results into attributesRegExRegExUse a regular expression to split the results into attributes NoneNoneDo not split resultstruefalsefalseNONEfalsefalseQUERY_PARSER_INPUTParser RegExChoice between a splitter and regex matcher used to parse the results of the query into attribute groups. NOTE: This is a multiline regular expression, therefore, the DFM should decide how to handle trailing new line characters.falsefalsefalseNONEfalsefalseKEY_GROUPKey lookup group (multiline / batch)When performing a batched lookup, the following RegEx numbered capture group or Column number will be used to match the whois server response with the lookup fieldfalsefalsefalseNONEfalsefalsenot foundWhere to route flow files if data enrichment query rendered no resultsfalsefoundWhere to route flow files after successfully enriching attributes with datafalseenrich.dns.record*.group*The captured fields of the Whois query response for each of the records receivedtruetrueINPUT_REQUIRED \ No newline at end of file