You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Ryan Hendrickson <ry...@gmail.com> on 2018/12/12 15:52:49 UTC
Include Section for Processor Breaking Changes in Changelog
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
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Pierre Villard <pi...@gmail.com>.
Hey Ryan,
That's usually something we try to document in the Migration Guidance page.
[1]
If you spot something missing, feel free to update it or let us know.
[1] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
Thanks,
Pierre
Le mer. 12 déc. 2018 à 16:53, Ryan Hendrickson <
ryan.andrew.hendrickson@gmail.com> a écrit :
> 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
>
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Mike Thomsen <mi...@gmail.com>.
Might be a good idea to add a Jira tag for this as well.
On Wed, Dec 12, 2018 at 1:00 PM Andy LoPresto <al...@gmail.com>
wrote:
> Ryan,
>
> That’s a good idea. I can take care of that right now. Thanks.
>
> Andy LoPresto
> alopresto@apache.org
> alopresto.apache@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.hendrickson@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 <bb...@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 <bb...@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
> >>> <ry...@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
> >>
>
>
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Andy LoPresto <al...@gmail.com>.
Ryan,
That’s a good idea. I can take care of that right now. Thanks.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Dec 12, 2018, at 9:50 AM, Ryan Hendrickson <ry...@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 <bb...@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 <bb...@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
>>> <ry...@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
>>
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Ryan Hendrickson <ry...@gmail.com>.
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 <bb...@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 <bb...@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
> > <ry...@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
>
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Bryan Bende <bb...@gmail.com>.
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 <bb...@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
> <ry...@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
Re: Include Section for Processor Breaking Changes in Changelog
Posted by Bryan Bende <bb...@gmail.com>.
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
<ry...@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