Re: NiFi 1.9.1 release contains a bug causing content repos to fill...
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> 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] > *Sent:* Wednesday, March 27, 2019 11:00 AM > *To:* 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. 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. > >
RE: NiFi 1.9.1 release contains a bug causing content repos to fill...
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] Sent: Wednesday, March 27, 2019 11:00 AM To: 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. 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.
ISPEnrichIP Issue
I am trying to use the latest GeoLite2 ASN database with the ISPEnrichIP processor but keep getting this error: 2019-03-29 18:09:26,149 WARN [Timer-Driven Process Thread-3] o.a.n.controller.tasks.ConnectableTask Administratively Yielding ISPEnrichIP[id=cbb088bd-0169-1000-1ab4-fb43b74a23c6] due to uncaught Exception: java.lang.UnsupportedOperationException: Invalid attempt to open a GeoLite2-ASN database using the isp method java.lang.UnsupportedOperationException: Invalid attempt to open a GeoLite2-ASN database using the isp method at org.apache.nifi.processors.maxmind.DatabaseReader.get(DatabaseReader.java:160) at org.apache.nifi.processors.maxmind.DatabaseReader.isp(DatabaseReader.java:242) at org.apache.nifi.processors.ISPEnrichIP.onTrigger(ISPEnrichIP.java:94) at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162) at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:205) at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Is the processor not compatible with GeoLite2?
NiFi Registry Not Auditing Denied Errors
I remember seeing something where we reduced the amount of auditing for access denied errors the NiFi Ranger plugin was doing. On a new installation with Registry 0.3.0 I'm not seeing any access denied errors at all despite the app log showing them. It's making it really hard to figure out what exactly is failing. I know it's related to the host access but the error log doesn't say what was being accessed. Basically I get log messages like these. 2019-03-30 09:56:54,817 INFO [NiFi Registry Web Server-20] o.a.n.r.w.m.AccessDeniedExceptionMapper identity[hdp31-df3.dev.example.com], groups[] does not have permission to access the requested resource. No applicable policies could be found. Returning Forbidden response. I could just give blanket access to everything but I prefer to be more precise. Thanks Shawn Weeks
