Sorry that was the duplicated ticket. The fix was in NIFI-12785 <https://issues.apache.org/jira/browse/NIFI-12785>
On Thu, Apr 11, 2024 at 2:02 PM Dan S <dsti...@gmail.com> wrote: > That is correct. This was fixed in NIFI-12842 > <https://issues.apache.org/jira/browse/NIFI-12842> > > On Thu, Apr 11, 2024 at 1:55 PM Martin Fong <martin.f...@toronto.ca> > 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/action/package_search?q=organization:${ORGANIZATION}%20AND%20name:${PACKAGE_NAME} >> >> >> >> It seems the %20AND%20 is causing the issue. Once removed the InvokeHTTP >> will work but wrong information is retrieved and will fail the whole >> process. It is working fine with 1.19.1. >> >> >> >> I have searched cloudera for similar issue: >> https://community.cloudera.com/t5/Support-Questions/Invoke-Http-with-url-containing-2F/m-p/385740 >> and they said this will be fixed in 1.26, is this correct? >> >> >> >> Please advise. >> >> Martin. >> >> On 2024/01/11 18:37:44 Pierre Villard wrote: >> > 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 consensus for a >> > release. So I guess this could happen in the next few weeks. I think >> we're >> > also getting close to the point where we would have 2.0-M2 so we'll >> > probably do that around the same time like we did with 1.24 and 2.0-M1. >> > >> > Thanks, >> > Pierre >> > >> > Le jeu. 11 janv. 2024 à 22:18, Martin Fong <ma...@toronto.ca> a >> > écrit : >> > >> > > Howdy, >> > > >> > > We are trying to migrate 1.19.1 to 1.24.0 as a pre-req to jump to >> 2.0.0-M1 >> > > later on. >> > > >> > > It seems there is a roadblock of "URL properties specified in >> components >> > > should be URL-encoded." We are trying to migrate as smoothly as >> possible >> > > without making many changes. >> > > >> > > NIFI-12513 seems to be fixed with 1.25.0/2.0.0 >> > > >> > > Is there a timeline for a fix as 1.24.1 or 1.25.0? >> > > >> > > Please advise, >> > > Martin Fong >> > > Enterprise Technical Support Specialist, Infrastructure & Platform >> (IAG) >> > > Technology Services Division, Technology Infrastructure Services >> > > City of Toronto >> > > 703 Don Mills Road, 2nd Floor >> > > Toronto, ON >> > > M3C 3N3 >> > > Tel: 416-397-7565 >> > > e-mail: martin.f...@toronto.ca<ma...@toronto.ca> >> > > >> > > This e-mail message is confidential and subject to copyright. Any >> > > unauthorized use or disclosure is prohibited. If you have received >> this >> > > email and are not the intended recipient, please advise and delete it. >> > > Thank you. >> > > >> > > >> > >> >
