Hi Shawn,
The 'No applicable policies could be found.' message can be logged
when a request is made against a resource which doesn't exist.
https://github.com/apache/nifi-registry/blob/master/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/security/authorization/r
Hello,
Even if there is a way to make this work, I would not recommend doing this.
Processors should not have access to internals of NiFI's framework
(i.e. nifi-framework-nar), they should only have access to what is
provided through the nifi-api which is the session and context.
If you start us
should have the 1.9.2 RC vote up tonight. All the artifacts are built.
Just need to craft the e-mail and push to dist folder.
Thanks
On Tue, Apr 2, 2019 at 1:25 PM Kevin Doran wrote:
> My apologies, the link I sent in my last message [1] may not be
> accessible unless you are signed into Jira.
I'm also trying to do this. Ive tried both in NiFi 171 and 191.
ExecuteScript doesnt seem to be able to load StandardFlowFileRecord, which
is strange since its part of nifi-framework-nar-*.nar which is in lib/.
I read a post saying somebody was using ExecuteGroovyScript which had
different imports
I hope someone has experienced the following problem and can point me to a
resolution. I have a NiFi flow in the 1.7.1.g environment. It appears that
my flow - contained in a Process Group - is no longer responding at the UI
level. In fact, none of my process group flows are responding in the UI.
