I have a custom processor, /SplitHl7v4Resources/, that splits out individual FHIR resources (Patients, Observations, Encounters, etc.) from great Bundle flowfiles. So, for a given flowfile, it's split into hundreds of smaller ones.

When I do this, I leave the existing NiFi attributes as they were on the original flowfile.

As I contemplate the uuid attribute, it occurs to me that I should find out what its *significance is for provenance and other potential debugging/tracing concerns*. I never really look at it, but, if there were some kind of melt-down in a production environment, would I care that it multiplied across hundreds of flowfiles besided the original one?

Also these two other NiFi attributes remain unchanged:

   filename
   path


I do garnish each flowfile with many pointed/significant new attributes like resource.type that are my own. In my processing, I don't care about NiFi's original attributes, but should I?

Thanks,
Russ

Reply via email to