Correct. Some lookup implementations give you the possibility to deal with several fields at once but it really depends of the impl. If you have strong use cases requiring improvements on the existing implementations, feel free to file a JIRA with as much details as possible.
Pierre 2018-04-27 11:48 GMT+02:00 françois lacombe <francois.laco...@dcbrain.com>: > Hi Pierre, > > Yes this makes sense. > I understand that file is a simple key=value text format. > > I may have different fields which can take different values for a single > key. > Example: field1: key=>value1 and field2: key=>value2 > Can I put this in the same file and same PropertiesFileLookupService or > should I create 2 different services with separate configurations ? > > Additonally I wish I can deal with several fields in the same LookupRecord > processor but it doesn't sound to be possible right ? > > All the best > > François > > 2018-04-27 11:31 GMT+02:00 Pierre Villard <pierre.villard...@gmail.com>: > >> Hi, >> >> You have to give the path to the properties file (key=value file) that >> will be used for your lookup service so that when using LookupRecord it >> will look for the value associated to the given key (with a dynamic >> property in the processor). >> >> Does it make sense? >> >> Pierre >> >> 2018-04-27 11:25 GMT+02:00 françois lacombe <francois.laco...@dcbrain.com >> >: >> >>> Hi, >>> >>> I'm trying to implement data enrichment with LookupRecord and >>> PropertiesFileLookupService. >>> >>> PropertiesFileLookupService asks me a configuration file but I can't >>> find any doc to know how to fill it. >>> Is it Avro schema or something ? >>> https://nifi.apache.org/docs/nifi-docs/components/org.apache >>> .nifi/nifi-lookup-services-nar/1.6.0/org.apache.nifi.lookup. >>> PropertiesFileLookupService/index.html >>> >>> >>> Thanks in advance for any hint >>> >>> >>> All the best >>> >>> François >>> >> >> >
