it does, thank you. -Stefán
On Tue, Dec 6, 2016 at 9:06 PM, Bryan Bende <bbe...@gmail.com> wrote: > Stefan, > > I believe the UUID attribute is treated as a special attribute internally > in NiFi. > > Depending how the data comes in to the system, such as site-to-site or > ListenHTTP, it will usually look to see if there is a UUID attribute (or a > head in the case of ListenHTTP) and use that UUID to create a provenance > RECEIVE event so that the original UUID is tracked, but then it generates a > new UUID for the actual flow file in NiFI. Also, if you try to use > UpdateAttribute to change the value of the UUID attribute, or if you try to > change it in a processor, I believe it throws an exception to prevent > anyone from doing this. > > So I think using your other attribute probably makes the most sense. Hope > this helps. > > -Bryan > > > On Sun, Dec 4, 2016 at 4:44 AM, Stefán Baxter <ste...@activitystream.com> > wrote: > > > Hi, > > > > We have been producing UUIDs for all messages flowing through Activity > > Stream that we call StreamId and they are of the same UUID version as > NiFi > > uses for FlowFiles. > > > > I tried to set the uuid attribute on "first contact" (in port) for NiFI > but > > it still, understandably, generates it's own UUID. > > > > Is there a way to have NiFi accept an external UUID or is it an > fundimental > > requirement of NiFi to generate on for it self? > > > > This is not important as I can set this as another attribute but I'm just > > looking to simplify things a bit :) for us and our tracability. > > > > Regards, > > -Stefán > > >
