Re: Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

I think you may be hitting a bug that was introduced in NiFi 1.25.0. See https://issues.apache.org/jira/browse/NIFI-12785 This issue has been resolved and will be fixed in NiFi 1.26.0. On Thu, Apr 11, 2024 at 1:55 PM Martin Fong wrote: > We have installed 1.25.0 and there is no deprecated mess

Re: Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

Sorry that was the duplicated ticket. The fix was in NIFI-12785 On Thu, Apr 11, 2024 at 2:02 PM Dan S wrote: > That is correct. This was fixed in NIFI-12842 > > > On Thu, Apr 11, 2024 at 1:55 PM

Re: Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

That is correct. This was fixed in NIFI-12842 On Thu, Apr 11, 2024 at 1:55 PM Martin Fong wrote: > We have installed 1.25.0 and there is no deprecated messages about this > bug but the URL-encoded does not work for this sample: > ${CKAN_URL}/api

RE: Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

We have installed 1.25.0 and there is no deprecated messages about this bug but the URL-encoded does not work for this sample: ${CKAN_URL}/api/action/package_search?q=organization:${ORGANIZATION}%20AND%20name:${PACKAGE_NAME} It seems the %20AND%20 is causing the issue. Once removed the Invok

Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

Hi Martin, I do think that having a NiFi 1.25 release soon would make sense. It would be nice to have a release that contains https://issues.apache.org/jira/browse/NIFI-12524 which can also be seen as an annoyance to upgrade to 2.0-M1. I'm happy to take care of the RM duties if there is a consens