When a result is obtained that contains a Record, this property determines whether the Record itself is inserted at the configured path or if the contents of the Record (i.e., the sub-fields) will be inserted at the configured path.
Specifies how to route records after a Lookup has completed
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) If not specified, the value that is returned from the Lookup Service will be ignored, except for determining whether the FlowFile should be routed to the 'matched' or 'unmatched' Relationship. The Lookup Service to use in order to lookup a value in each RecordĪ RecordPath that points to the field whose value should be updated with whatever value is returned from the Lookup Service. Specifies the Controller Service to use for writing out the recordsĬontroller Service API: LookupService Implementations: MongoDBLookupService HBase_2_RecordLookupService KuduLookupService CouchbaseRecordLookupService SimpleKeyValueLookupService CouchbaseKeyValueLookupService PropertiesFileLookupService RestLookupService SimpleDatabaseLookupService HBase_1_1_2_RecordLookupService CSVRecordLookupService SimpleCsvFileLookupService ElasticSearchLookupService DatabaseRecordLookupService SimpleScriptedLookupService IPLookupService ElasticSearchStringLookupService XMLFileLookupService ScriptedLookupService HBase_1_1_2_ListLookupService DistributedMapCacheLookupService Specifies the Controller Service to use for reading incoming dataĬontroller Service API: RecordSetWriterFactory Implementations: CSVRecordSetWriter JsonRecordSetWriter AvroRecordSetWriter ParquetRecordSetWriter XMLRecordSetWriter FreeFormTextRecordSetWriter ScriptedRecordSetWriter RecordSetWriterLookup
NameĬontroller Service API: RecordReaderFactory Implementations: GrokReader JsonTreeReader ParquetReader ReaderLookup WindowsEventLogReader CEFReader SyslogReader AvroReader XMLReader ScriptedReader JsonPathReader Syslog5424Reader CSVReader
The table also indicates any default values, and whether a property supports the NiFi Expression Language. Any other properties (not in bold) are considered optional. In the list below, the names of required properties appear in bold. Lookup, enrichment, route, record, csv, json, avro, database, db, logs, convert, filter Properties: Please note, however, that if the results returned by the LookupService are not accounted for in your schema (specifically, the schema that is configured for your Record Writer) then the fields will not be written out to the FlowFile. I.e., it will not overwrite an existing value in the Record with a null value. If there is no match in the configured LookupService, then no fields will be updated. If one or more fields match the Result RecordPath, all fields that match will be updated. If multiple values are returned by the RecordPath, then the Record will be routed to the 'unmatched' relationship (or 'success', depending on the 'Routing Strategy' property's configuration). Each property that is added will have an entry added to a Map, where the name of the property becomes the Map Key and the value returned by the RecordPath becomes the value for that key. The "coordinates" to use for looking up a value in the Lookup Service are defined by adding a user-defined property. Regardless, the Record is then routed to either the 'matched' relationship or 'unmatched' relationship (if the 'Routing Strategy' property is configured to do so), indicating whether or not a result was returned by the LookupService, allowing the processor to also function as a Routing processor. In this case, the processor functions as an Enrichment processor. If a result is returned by the LookupService, that result is optionally added to the Record. Extracts one or more fields from a Record and looks up a value for those fields in a LookupService.