Can a patch be made available to fix this issue for existing 1.9.1 installations?
From: Joe Witt <joe.w...@gmail.com> Sent: Saturday, March 30, 2019 12:32 PM To: users@nifi.apache.org 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 <mathieu.louis-ferdin...@morganstanley.com<mailto:mathieu.louis-ferdin...@morganstanley.com>> wrote: Hi Joe, Do you have an idea of the timeline for 1.9.2 RC? Cheers, Mathieu. From: Joe Witt [mailto:joe.w...@gmail.com<mailto:joe.w...@gmail.com>] Sent: Wednesday, March 27, 2019 11:00 AM To: users@nifi.apache.org<mailto:users@nifi.apache.org> 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: http://www.morganstanley.com/disclaimers<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.morganstanley.com_disclaimers%26d%3DDwMFaQ%26c%3DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w%26r%3DWm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU%26m%3DWH9htJbf5xpYmBs-0gksemH94g9Qd952TPkXN9K5DCw%26s%3DTne_-4xOmvNICuISr1XTjeysHp3k_mLjh8bZmLqRMN8%26e%3D&data=02%7C01%7Cwilliam.gosse%40aifoundry.com%7C8db84eb923e24b14bfd408d6b52d4cbc%7Cd29b7a9b6edb472099a83c5c6c3eeeb0%7C0%7C0%7C636895603512840336&sdata=RSmV1mrBUuVmce4oVQRH%2FMtjOu5dgQafbUFHxlPyG1U%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.
