Hi Rotem,
You are correct, the WriteAheadProvenanceRepository returns provenance
event FlowFile UUID value differently than the default
PersistentProvenanceRepository.
Here is the lines of code that set FlowFile UUID for the provenance events.
Hi,
We had another server that was not experiencing this bug, but when we
changed to the WriteAheadProvenanceRepository (like on the server where we
first noticed this) we did see it. Have there been changes in that
implementation? Could this cause what we are seeing?
Thanks!
Rotem
On 28 Dec
Hi Rotem,
When I tested it with NiFi 1.5.0-SNAPSHOT, the REPLAY event has its
FlowFile UUID as the parent (original) FlowFile UUID as expected.
Type
REPLAY
FlowFile Uuid
8c61fdd7-c084-4756-946c-f5669dc4442d
File Size
4 bytes
Component Id
9abc21e3-0160-1000-6d6f-a1c408f75b7a
Component Name
Hi!
I have been using nifi for a while, and have recently upgraded from 1.2.0
to 1.4.0.
I am having problems with replay events. In version 1.2.0, the UUID of a
replay event is the id of the original flowfile that is being replayed.
This is the behavior that is documented in the developer guid (
