I have just found https://issues.apache.org/jira/browse/NIFI-10203, it's a know issue resolved in 1.17.0. sorry for spamming the list.

On 22-09-01 13:41, Lars Winderling wrote:
Dear community,

we have recently upgraded from 1.14.0 to 1.16.3. And the automatic UUID generation on CLONE events seems to have changed. When sending a flowfile from a source (processor or port) using the same relationship to multiple sinks, the cloned flowfiles all have the same UUID. Before the upgrade, the flowfiles all received individual flowfiles on CLONE. To be precise: one flowfile did retain the old UUID, the clones got new ones. Now all share the same.

I have created a sample flow consisting of GenerateFlowFile and ExecuteGroovyScript. The executed script
 reads as follows:

-----------------------------------------

def ff = session.get()
if (!ff) return

log.error("\n{}", [ff.getAttribute("uuid")] as Object[])

session.transfer(ff, REL_SUCCESS)

-----------------------------------------

You can find an image and the flow definition at https://cloud.winderling.net/s/tzqJBqJzF4fawZN. Please execuse the slow initial loading time, it's a low-cost vm.

So my question is: is that a bug or a feature? Since duplicate UUIDs lead to many issues, I expect it's the former.

Thank you in advance!
Best,
Lars

-----------------------------------

OS: debian 10
NiFi: 1.16.3
java: temurin 11
openjdk version "11.0.16.1" 2022-08-12
OpenJDK Runtime Environment Temurin-11.0.16.1+1 (build 11.0.16.1+1)
OpenJDK 64-Bit Server VM Temurin-11.0.16.1+1 (build 11.0.16.1+1, mixed mode)



Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to