[
https://issues.apache.org/jira/browse/NIFI-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-13563:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add endpoint to return most recent provenance events for a processor
> invocation
> -------------------------------------------------------------------------------
>
> Key: NIFI-13563
> URL: https://issues.apache.org/jira/browse/NIFI-13563
> Project: Apache NiFi
> Issue Type: Task
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When building a flow, the ability to click "Replay Last Event" can be
> incredibly powerful and convenient, giving the user the ability to more
> quickly verify changes. However, it sometimes can fail, depending on what the
> latest event was. For example, a JOIN event cannot be replayed because it
> would mean re-queuing potentially huge numbers of FlowFiles. Often, though, a
> Processor will emit multiple events in the same invocation.
> To account for this, instead of only retrieving the last event for a
> Processor, retrieve the last "event set" - that is, all events from the last
> invocation of a Processor and iterate through all of them until able to
> replay an event.
> In addition to simply replaying the event, though, we should have the ability
> to retrieve those latest events, as building a flow typically means that we
> want to know what "just happened".
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
