My apologies, the link I sent in my last message [1] may not be accessible unless you are signed into Jira. If you cannot view that link, see [2]. [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345213
On Tue, Apr 2, 2019 at 1:18 PM Kevin Doran <[email protected]> wrote: > > For what it's worth, v1.9.2 is going to include a number of bug fixes > in addition to NIFI-6150. While the other bugs are not nearly as > critical (depending on your usage of NiFi), all the more the reason to > upgrade to 1.9.2 rather than patching a 1.9.1 install. For a full list > of what's been included in the RC for 1.9.2 so far, see [1]: > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12345213 > > Cheers, > Kevin > > On Tue, Apr 2, 2019 at 1:04 PM William Gosse > <[email protected]> wrote: > > > > "Although I'm not sure why that would be preferred over getting the > > officially released fix in 1.9.2" - I don't prefer applying a patch but I > > do have some systems already setup with 1.9.1. I'll probably bite the > > bullet and moved to 1.9.2 as soon as its available. We are in the process > > of containerizing nifi with docker so hopefully that will make moving to a > > newer release not a big deal. > > > > -----Original Message----- > > From: Bryan Bende <[email protected]> > > Sent: Tuesday, April 2, 2019 12:25 PM > > To: [email protected] > > Subject: Re: NiFi 1.9.1 release contains a bug causing content repos to > > fill... > > > > [CAUTION: This email originated from outside of Kodak Alaris. Do not click > > links or open attachments unless you recognize the sender and know the > > content is safe.] ________________________________ > > > > The associated JIRA is NIFI-6150 [1] and it leads to the content repo not > > properly cleaning up and eventually filling up disks. > > > > There will be a 1.9.2 release to address this. Of course you are free to > > take the patch for the fix [2], apply it to the 1.9.1 release tag [3], and > > build your own fix, although I'm not sure why that would be preferred over > > getting the officially released fix in 1.9.2. > > > > [1] > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__issues.apache.org_jira_browse_NIFI-2D6150%26d%3DDwIFaQ%26c%3DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w%26r%3DWm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU%26m%3DIcEOLvLqMRwVGHZrj8MeEuGvHHj6WxiOyETFetIDgS8%26s%3D26O4gEjALxwRdlVmLjatxiCTiApEi5UN76no-9D--yQ%26e&data=02%7C01%7Cwilliam.gosse%40aifoundry.com%7C65f8067fa3cf41f6eb6e08d6b78b241d%7Cd29b7a9b6edb472099a83c5c6c3eeeb0%7C0%7C0%7C636898205580491866&sdata=emHvuWSerL0yVKRSam5metw3KBFYCphFpI%2BlHEpfmOc%3D&reserved=0= > > [2] > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__patch-2Ddiff.githubusercontent.com_raw_apache_nifi_pull_3391.patch%26d%3DDwIFaQ%26c%3DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w%26r%3DWm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU%26m%3DIcEOLvLqMRwVGHZrj8MeEuGvHHj6WxiOyETFetIDgS8%26s%3D2_4CR7XulBNmfR2MlPlDcdTgKD6NIiP6S_u8YG17qO0%26e&data=02%7C01%7Cwilliam.gosse%40aifoundry.com%7C65f8067fa3cf41f6eb6e08d6b78b241d%7Cd29b7a9b6edb472099a83c5c6c3eeeb0%7C0%7C0%7C636898205580491866&sdata=dFHMeTTGT%2FwzbfoPBizqRUJ1dMXhoGS2Q1d%2F3v%2FOBx8%3D&reserved=0= > > [3] > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__github.com_apache_nifi_tree_rel_nifi-2D1.9.1%26d%3DDwIFaQ%26c%3DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w%26r%3DWm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU%26m%3DIcEOLvLqMRwVGHZrj8MeEuGvHHj6WxiOyETFetIDgS8%26s%3DVP_sGtxIOZIh_pm1wipeONZ6l1i3G5epzYUT_J_K2dk%26e&data=02%7C01%7Cwilliam.gosse%40aifoundry.com%7C65f8067fa3cf41f6eb6e08d6b78b241d%7Cd29b7a9b6edb472099a83c5c6c3eeeb0%7C0%7C0%7C636898205580491866&sdata=9B2wS%2FXeHsS9U02A72CKE4MWcr9mQXXY2LIGnFD8ME0%3D&reserved=0= > > > > On Tue, Apr 2, 2019 at 12:17 PM William Gosse <[email protected]> > > wrote: > > > > > > Also can someone explain more what this issue is and how serious it is. > > > > > > Can a patch be made available to fix this issue for existing 1.9.1 > > > installations? > > > > > > > > > > > > From: Joe Witt <[email protected]> > > > Sent: Saturday, March 30, 2019 12:32 PM > > > To: [email protected] > > > Subject: Re: NiFi 1.9.1 release contains a bug causing content repos to > > > fill... > > > > > > > > > > > > [CAUTION: This email originated from outside of Kodak Alaris. Do not > > > click links or open attachments unless you recognize the sender and > > > know the content is safe.] > > > > > > ________________________________ > > > > > > mathieu > > > > > > > > > > > > just a matter of finding the chunk of time to knock it out. perhaps this > > > evening. > > > > > > > > > > > > thanks > > > > > > On Sat, Mar 30, 2019, 11:27 AM Louis-Ferdinand, Mathieu > > > <[email protected]> wrote: > > > > > > Hi Joe, > > > > > > > > > > > > Do you have an idea of the timeline for 1.9.2 RC? > > > > > > > > > > > > Cheers, > > > > > > Mathieu. > > > > > > > > > > > > From: Joe Witt [mailto:[email protected]] > > > Sent: Wednesday, March 27, 2019 11:00 AM > > > To: [email protected] > > > Subject: NiFi 1.9.1 release contains a bug causing content repos to > > > fill... > > > > > > > > > > > > All, > > > > > > > > > > > > We will work to promptly produce an Apache NiFi 1.9.2 release which will > > > correct a regression introduced in the 1.9.1 release. The issue, > > > NIFI-6150 has been identified and fixed on master and once further > > > testing confirms we're good we'll get the RC going. > > > > > > > > > > > > I've updated the release guide to discourage use of 1.9.1 until the fix > > > is out. > > > > > > > > > > > > Thanks > > > > > > Joe > > > > > > > > > > > > ________________________________ > > > > > > NOTICE: Morgan Stanley is not acting as a municipal advisor and the > > > opinions or views contained herein are not intended to be, and do not > > > constitute, advice within the meaning of Section 975 of the Dodd-Frank > > > Wall Street Reform and Consumer Protection Act. If you have received this > > > communication in error, please destroy all electronic and paper copies > > > and notify the sender immediately. Mistransmission is not intended to > > > waive confidentiality or privilege. Morgan Stanley reserves the right, to > > > the extent required and/or permitted under applicable law, to monitor > > > electronic communications, including telephone calls with Morgan Stanley > > > personnel. This message is subject to the Morgan Stanley General > > > Disclaimers available at the following link: > > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.morganstanley.com_disclaimers%26d%3DDwIFaQ%26c%3DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w%26r%3DWm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU%26m%3DIcEOLvLqMRwVGHZrj8MeEuGvHHj6WxiOyETFetIDgS8%26s%3D5uma0Jh97GhlqQ5opQicKFR9FLMXxKuVPLE281ShF1w%26e&data=02%7C01%7Cwilliam.gosse%40aifoundry.com%7C65f8067fa3cf41f6eb6e08d6b78b241d%7Cd29b7a9b6edb472099a83c5c6c3eeeb0%7C0%7C0%7C636898205580491866&sdata=%2F5H6GhMvNspNOtp%2Fhmot2CzTWNIk6LBppxv%2FwvFL4BQ%3D&reserved=0=. > > > If you cannot access the links, please notify us by reply message and > > > we will send the contents to you. By communicating with Morgan Stanley > > > you acknowledge that you have read, understand and consent, (where > > > applicable), to the foregoing and the Morgan Stanley General Disclaimers.
