Hi Toivo, The bulletins do not contain a specific field identifying a flowfile because not every bulletin is caused by or directly related to an individual flowfile. Bulletins can be generated by processors, controller services, reporting tasks, etc. and may not be due to a flowfile error.
In the situations where the bulletin is caused by a flowfile exception, the flowfile uuid and resource claim are often included in the bulletin message, but you will have to parse the text to extract these in order to perform further processing/queries. Most bulletins are generated automatically from exceptions being caught and logged via ComponentLog, which are then translated via the LogObserver implementations [1]. [1] https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/logging/ProcessorLogObserver.java <https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/logging/ProcessorLogObserver.java> Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 21, 2017, at 8:06 AM, Toivo Adams <[email protected]> wrote: > > I am creating custom Reporting Task. > Reporting Task will read Bulletins. > But I am missing something obvious, bulletin does not have reference to > FlowFile? > I mean Bulletin was generated during processing some FlowFile and I want to > find FlowFile attributes. > Is this possible? > > Thanks > Toivo > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Bulletin-and-related-FlowFile-tp14488.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
signature.asc
Description: Message signed with OpenPGP using GPGMail
