[
https://issues.apache.org/jira/browse/NIFI-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-13563:
------------------------------
Issue Type: Task (was: Bug)
> Replay Last Event sometimes fails
> ---------------------------------
>
> 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
>
> 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.
> This also provides some value, in that we could potentially return the latest
> "event set" for consumption, as it may provide value over the entirety of all
> events for the Processor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
