Ryan, That’s a good idea. I can take care of that right now. Thanks.
Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Dec 12, 2018, at 9:50 AM, Ryan Hendrickson > <ryan.andrew.hendrick...@gmail.com> wrote: > > Thanks, I'll keep my eyes on that Migration Guidance in the future as well. > > It'd be nice if on the NiFi Downloads page ( > https://nifi.apache.org/download.html) the Migration Guidance was linked > there too, like the Release Notes. > > Ryan > > On Wed, Dec 12, 2018 at 11:54 AM Bryan Bende <bbe...@gmail.com> wrote: > >> I added it to the section for 1.4.0 to 1.5.0. >> On Wed, Dec 12, 2018 at 11:50 AM Bryan Bende <bbe...@gmail.com> wrote: >>> >>> Ryan, >>> >>> Thanks for mentioning this. Changes like this should really be >>> captured in the migration guidance for the given release, but it looks >>> like this was not in the 1.5.0 guidance. >>> >>> https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance >>> >>> -Bryan >>> >>> On Wed, Dec 12, 2018 at 10:53 AM Ryan Hendrickson >>> <ryan.andrew.hendrick...@gmail.com> wrote: >>>> >>>> Hi, >>>> I recently upgraded a NiFi from 1.4 to 1.8 and found a breaking >> change. >>>> The ExecuteStreamCommand processor, in NiFi 1.5, introduced a new >>>> relationship for errors (NIFI-4559 >>>> <https://issues.apache.org/jira/browse/NIFI-4559>). The >> consequence: We >>>> missed that 1 of our many processors moved into an invalid state. A >> week >>>> later, we notice that part of our flow wasn't processing data because >> it's >>>> waiting for the new relationship to be drawn. >>>> >>>> It'd be great if in the Release Notes >>>> < >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12341668 >>> >>>> changes >>>> like these are highlighted under a specific section, such as "Breaking >>>> changes." >>>> >>>> Thanks >>>> Best, >>>> Ryan >>
