Re: Apache NiFi

[Aldrin Piri]

Based on the versions that worked/didn't work, I am assuming this concerns
the host header protections that was covered in NIFI-4761 and then made
configurable to our Docker image in NIFI-4788.  What changed is detailed in
the admin guide toward the bottom of the Proxy Configuration section [3].

If this doesn't quite seem to coincide with what you are experiencing, more
information (inclusive of compose file, if possible) would be great.

[1] https://issues.apache.org/jira/browse/NIFI-4761
[2] https://issues.apache.org/jira/browse/NIFI-4788
[3]
https://github.com/mcgilman/nifi/blob/acb19a91fc7908e10dbc2b4364daa1657fc7657b/nifi-docs/src/main/asciidoc/administration-guide.adoc#proxy-configuration

On Wed, Dec 12, 2018 at 1:09 PM Mike Thomsen  wrote:

> Samir,
>
> Can you be more specific, preferably posting some logs?
>
> Thanks,
>
> Mike
>
> On Wed, Dec 12, 2018 at 12:13 PM Zaciragic, Samir * <
> samir.zacira...@fda.hhs.gov> wrote:
>
> > Hello,
> >
> > We are FDA docker support team trying to assist internal teams to onboard
> > their applications. We were able to pull latest apache NiFi (1.8.0) and
> run
> > container manually, but we faced an issue to use docker-compose to start
> > the service. One of our teammates found that older version of apache Nifi
> > (1.4.0) works, but none of newer versions due to the fact that newer
> > version have some security features that prevent docker service to run
> > properly.
> >
> > Is there some particular setup we are missing, that would help run the
> > service with newer version? Any assistance would be greatly appreciated.
> >
> > Thank you!
> >
>

Re: Include Section for Processor Breaking Changes in Changelog

[Mike Thomsen]

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 
wrote:

> 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  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  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
> >>>  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
>  ).  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=12341668
> >>>
>  changes
>  like these are highlighted under a specific section, such as "Breaking
>  changes."
> 
>  Thanks
>  Best,
>  Ryan
> >>
>
>

Re: Apache NiFi

[Mike Thomsen]

Samir,

Can you be more specific, preferably posting some logs?

Thanks,

Mike

On Wed, Dec 12, 2018 at 12:13 PM Zaciragic, Samir * <
samir.zacira...@fda.hhs.gov> wrote:

> Hello,
>
> We are FDA docker support team trying to assist internal teams to onboard
> their applications. We were able to pull latest apache NiFi (1.8.0) and run
> container manually, but we faced an issue to use docker-compose to start
> the service. One of our teammates found that older version of apache Nifi
> (1.4.0) works, but none of newer versions due to the fact that newer
> version have some security features that prevent docker service to run
> properly.
>
> Is there some particular setup we are missing, that would help run the
> service with newer version? Any assistance would be greatly appreciated.
>
> Thank you!
>

Re: Include Section for Processor Breaking Changes in Changelog

[Andy LoPresto]

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 
>  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  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  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
>>>  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
 ).  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=12341668
>>> 
 changes
 like these are highlighted under a specific section, such as "Breaking
 changes."
 
 Thanks
 Best,
 Ryan
>> 

Apache NiFi

[Zaciragic, Samir *]

Hello,

We are FDA docker support team trying to assist internal teams to onboard their 
applications. We were able to pull latest apache NiFi (1.8.0) and run container 
manually, but we faced an issue to use docker-compose to start the service. One 
of our teammates found that older version of apache Nifi (1.4.0) works, but 
none of newer versions due to the fact that newer version have some security 
features that prevent docker service to run properly.

Is there some particular setup we are missing, that would help run the service 
with newer version? Any assistance would be greatly appreciated.

Thank you!

Re: Include Section for Processor Breaking Changes in Changelog

[Bryan Bende]

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  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
>  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
> > ).  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
> > 
> > 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

[Pierre Villard]

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.hendrick...@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
> ).  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=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

[Bryan Bende]

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
 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
> ).  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
> 
> changes
> like these are highlighted under a specific section, such as "Breaking
> changes."
>
> Thanks
> Best,
> Ryan

Include Section for Processor Breaking Changes in Changelog

[Ryan Hendrickson]

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
).  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

changes
like these are highlighted under a specific section, such as "Breaking
changes."

Thanks
Best,
Ryan