[
https://issues.apache.org/jira/browse/NIFI-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060006#comment-16060006
]
ASF subversion and git services commented on NIFI-4017:
-------------------------------------------------------
Commit 5c755c006b37c0b65cce930d291c747155f58916 in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5c755c0 ]
NIFI-4017: Emit provenance event from Notify.
This closes #1890.
Signed-off-by: Andy LoPresto <[email protected]>
> 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.4.14#64029)
