You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Michael Hogue (Jira)" <ji...@apache.org> on 2019/12/17 02:56:00 UTC
[jira] [Updated] (NIFI-6851) Improve Provenance RECEIVE and FETCH
events to allow for specifics on how flowfile was RECEIVE'ed/FETCH'ed
[ https://issues.apache.org/jira/browse/NIFI-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Hogue updated NIFI-6851:
--------------------------------
Status: Patch Available (was: In Progress)
> Improve Provenance RECEIVE and FETCH events to allow for specifics on how flowfile was RECEIVE'ed/FETCH'ed
> ----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6851
> URL: https://issues.apache.org/jira/browse/NIFI-6851
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.10.0
> Reporter: Nissim Shiman
> Assignee: Michael Hogue
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently there is no way to know if a Provenance RECEIVE or FETCH event is the result of an active (i.e. GetFTP, FetchFTP, GetHTTP), passive (i.e. ListenHTTP) or query (i.e. GetMongo) event.
> There was a discussion on the dev mailing lists regarding the most graceful way to do this [1] [2],
>
> At this time the smoothest path forward is to keep the current method signatures of receive() and fetch() as is in ProvenanceReporter.java [3]
> and to add new fetch() and receive()'s with a new parameter:
> receive(...,ACTIVE|PASSIVE|QUERY)
> If not specified it would be UNSPECIFIED.
> (Thank You [~joewitt] for this solution)
>
>
> [1] [https://mail-archives.apache.org/mod_mbox/nifi-dev/201910.mbox/browser] , topic of PULL ProvenanceEvent
> [2] [https://mail-archives.apache.org/mod_mbox/nifi-dev/201911.mbox/browser] , topic of Re: PULL ProvenanceEvent
> [3] [https://github.com/apache/nifi/blob/master/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)