Re: unwedgeable flow caused by "Cannot create Provenance Event Record because FlowFile UUID is not set"

Thank you Chris Will be addressed shortly Oleg > On Jun 14, 2016, at 9:56 AM, McDermott, Chris Kevin (MSDU - > STaTS/StorefrontRemote) wrote: > > Thanks, Oleg. I’ve created NIFI-2015. > > > Regards, > > Chris McDermott > > Remote Business Analytics >

Re: unwedgeable flow caused by "Cannot create Provenance Event Record because FlowFile UUID is not set"

Thanks, Oleg. I’ve created NIFI-2015. Regards, Chris McDermott Remote Business Analytics STaTS/StoreFront Remote HPE Storage Hewlett Packard Enterprise Mobile: +1 978-697-5315 https://www.storefrontremote.com On 6/13/16, 3:10 PM, "Oleg Zhurakousky" wrote:

Re: unwedgeable flow caused by "Cannot create Provenance Event Record because FlowFile UUID is not set"

Chris The fact that your flow is hosed means this is a bug. IMHO corrupted FlowFile should not render NiFi unavailable. So please raise the JIRA. Also, i think the real question here is not how the FF got corrupted but the fact that corrupted FF rendered NIFI unavailable and that is the core

unwedgeable flow caused by "Cannot create Provenance Event Record because FlowFile UUID is not set"

2016-06-13 17:33:30,275 ERROR [Timer-Driven Process Thread-4] o.a.n.p.attributes.UpdateAttribute java.lang.IllegalStateException: Cannot create Provenance Event Record because FlowFile UUID is not set at