Hi Brett, Thanks for your feedback on the “Add Processor” window. I’m sorry you had trouble identifying the right processor to use for your data flow.
There are tags on the left of the “Add Processor” window that categorize many of the processors into functional groups. For example, selecting the “attributes” tag would limit the processors listed to the those related to attributes. Additionally, there is a Filter field at the top that can also be used to search processors. More information on using tags and filters can be found in the documentation [1]. Having said that, the UX of finding/adding a processor can definitely be improved. There are two Jiras related to this effort that I am aware of [2][3]. If you have the opportunity to review those proposed improvements, additional thoughts/suggestions are welcomed and greatly appreciated! [1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#adding-components-to-the-canvas [2] https://issues.apache.org/jira/browse/NIFI-3338 [3] https://issues.apache.org/jira/browse/NIFI-4249 -Drew > On Jan 4, 2018, at 4:33 PM, Brett Ryan <brett.r...@gmail.com> wrote: > > Ooo, i shall take a look at this, that sounds great. > > Yeah, my inexperience is probably a sore point. You know what would be great, > either in the add processor browser to have categories to find processors. > Trying to find enrichment processors only is probably the hardest part of > identifying the right processor. > > Where I’m working they’re on nifi 1.1 and iirc they had > 200 processors. > It’s also possible that newer processors are available in newer versions. > > >> On 5 Jan 2018, at 04:01, Joey Frazee <joey.fra...@icloud.com> wrote: >> >> Andy, Brett, >> >> Taking a quick glance at the code it looks like it's enriching attributes >> from a database according to a query. >> >> If that's correct, there's a LookupAttribute processor that delegates >> lookups to a "LookupService" and adds attributes without altering content. >> There are a variety of these LookupServices included. I think what you >> implemented would make sense as a LookupService and then you could just >> configure the processor to use that. It could also be used with LookupRecord >> then too so there'd be a double payoff. >> >> -joey >> >>> On Jan 4, 2018, 8:44 AM -0800, Andy LoPresto <alopre...@apache.org>, wrote: >>> Hi Brett, >>> >>> It’s great that you found it easy to write a new processor for Apache NiFi. >>> It is probably an indicator that we need to improve >>> education/evangelism/documentation, however, that you did not find >>> UpdateAttribute [1], which should do exactly what you were looking for. >>> >>> [1] >>> https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.4.0/org.apache.nifi.processors.attributes.UpdateAttribute/index.html >>> >>> Andy LoPresto >>> alopre...@apache.org >>> alopresto.apa...@gmail.com >>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> >>>> On Jan 4, 2018, at 7:03 AM, Brett Ryan <brett.r...@gmail.com> wrote: >>>> >>>> Hi all, having used NiFi for a couple days I wanted to add some attributes >>>> to a FlowFile while not altering the contents of that FlowFile. >>>> >>>> I had suggestions to use a script processor but that just sounded like a >>>> hack which could become a nuisance to replicate. >>>> >>>> Anyway, I figured I'd write a processor to do this, anyone interested you >>>> can find it here. >>>> >>>> https://github.com/brettryan/nifi-drunken-bundle >>>> >>>> Feel free to do with it what you please. >>>> >>>> I've published to maven central but it will take a day to appear in the >>>> search. >>>> >>>> <dependency> >>>> <groupId>com.drunkendev</groupId> >>>> <artifactId>nifi-drunken-nar</artifactId> >>>> <version>1.0.0</version> >>>> <type>nar</type> >>>> </dependency> >>>> <dependency> >>>> <groupId>com.drunkendev</groupId> >>>> <artifactId>nifi-drunken-processors</artifactId> >>>> <version>1.0.0</version> >>>> </dependency> >>>> <dependency> >>>> <groupId>com.drunkendev</groupId> >>>> <artifactId>nifi-drunken-bundle</artifactId> >>>> <version>1.0.0</version> >>>> <type>pom</type> >>>> </dependency> >>>> >>>
