[
https://issues.apache.org/jira/browse/NIFI-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020784#comment-15020784
]
ASF subversion and git services commented on NIFI-1196:
-------------------------------------------------------
Commit 1580edb558e96dc49a40b50e8f5fd7e31e61371d in nifi's branch
refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1580edb ]
NIFI-1196 Correcting treatment of FETCH events as a continuation of a lineage
trail and not the start of a new one.
Reviewed by Tony Kurc ([email protected])
> FETCH Events are not properly handled in the framework and UI
> -------------------------------------------------------------
>
> Key: NIFI-1196
> URL: https://issues.apache.org/jira/browse/NIFI-1196
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Affects Versions: 0.3.0
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Fix For: 0.4.0
>
> Attachments:
> 0001-NIFI-1196-Providing-handling-of-FETCH-provenance-eve.patch,
> Get_Site_-_InvokeHTTP_-_Fetch.xml, NIFI-1196.001.patch, NIFI-1196.002.patch
>
>
> When the FETCH ProvenanceEventType was incorporated some of its handling was
> not propagated throughout the framework. This is chiefly inclusive of:
> * Presenting transit uri in the Provenance event info within the UI
> * Writing/Reading provenance events into the StandardRecordReader/Writer
> * Handling in the StandardProcessSession for counting flowfiles in/out and
> their bytes
> The net result is that unique properties, in this case believed to be only
> transit URI were never persisted and/or received.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
