mirror of https://github.com/apache/nifi.git
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 (tkurc@apache.org)
This commit is contained in:
parent
cdd2c4f22c
commit
1580edb558
|
@ -259,6 +259,7 @@ public class StandardLineageResult implements ComputeLineageResult {
|
|||
case FORK:
|
||||
case JOIN:
|
||||
case REPLAY:
|
||||
case FETCH:
|
||||
case CLONE: {
|
||||
// For events that create FlowFile nodes, we need to create the FlowFile Nodes and associated Edges, as appropriate
|
||||
for (final String childUuid : record.getChildUuids()) {
|
||||
|
@ -288,7 +289,6 @@ public class StandardLineageResult implements ComputeLineageResult {
|
|||
}
|
||||
break;
|
||||
case RECEIVE:
|
||||
case FETCH:
|
||||
case CREATE: {
|
||||
// for a receive event, we want to create a FlowFile Node that represents the FlowFile received
|
||||
// and create an edge from the Receive Event to the FlowFile Node
|
||||
|
|
Loading…
Reference in New Issue