[ https://issues.apache.org/jira/browse/NIFI-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Kawamura updated NIFI-4017: -------------------------------- Status: Patch Available (was: Open) > Notify processor does not have any data provenance generated > ------------------------------------------------------------ > > Key: NIFI-4017 > URL: https://issues.apache.org/jira/browse/NIFI-4017 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Affects Versions: 1.2.0 > Reporter: Koji Kawamura > Assignee: Koji Kawamura > > Notify doesn't emit any provenance event because it doesn't do any update > operation with incoming FlowFiles. There are other processors those don't > create any provenance (e.g. LogAttribute), and those are probably fine, but > since Notify can be an important part of controlling flow, it's easy to > imagine users to search data provenance event for Notify. > Then, which provenance event does suit what Notify does? I looked at > PutDistributedMapCache processor. PutDistributedMapCache writes an attribute > named 'cached' as true when it updates cache. I think Notify can use the same > approach to create provenance events by adding 'notified' true attribute > value, as it does the same thing with PutDistributedMapCache in terms of > updating an entry in distributed cache. -- This message was sent by Atlassian JIRA (v6.3.15#6346)