Re: Problem with property descriptor in InvokeScriptedProcessor

Hi Denes, Yes, that was it. I missed the import you mentioned. Thanks a lot for your help and also for suggesting setting the logging level to debug! Best regards, Elemir From: Denes Arvay Reply-To: "users@nifi.apache.org" Date: Thursday, 21 March 2019 at 6:22 pm To: "users@nifi.apache.org"

Re: Using NiFi Expression Language outside of NiFi

Tim, Sorry I lost track of this, I meant to respond earlier. If you can use a tool/language that brings in dependencies easily, such as Groovy, then using NiFi Expression Language to evaluate expressions is fairly straightforward, here's a Groovy script I use to do just that (the extra gravy is

Re: Using NiFi Expression Language outside of NiFi

Sorry for the delay in responding. After looking at a few different options it looks like it will be pretty easy to accomplish what we need using Java Unified Expression Language . -- Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Nifi backup & recovery

Hello All, I would like to have the ability to recreate the nifi system and wondering what status I need to store/preserver. It's a single node system at this time. I am backing up the following at this time. Repos: Disk back up of repositories directories - content, provenence & flowfile,

Re: sensitive variable values ?

Are you not able to update the properties for the controller service. It looks like you use something like PUT /controller-services/{id} with some json kinda like this. { "revision": {…}, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}],

Re: sensitive variable values ?

I don't see how to do it for service from NiFi REST api... Any suggestions? Thank you > >

RE: Automate the Enablement of a StandardHttpContextMap

Ok I got this working by configuring each Http component's StandardHttpContextMap individual instead having them all ganged all onto one. Each of the StandardHttpContextMap is stills coped for the process group that all the components are in. I'll admit I'm still a little shaky on controller

Re: sensitive variable values ?

Sensitive variables is something we'd like to support, but we currently don't have that capability yet. If you are using a script to create components, or to instantiate templates, you should be able to set the property values of those components using the REST API. You would be making the same

Re: sensitive variable values ?

Hello The variables of a pg are not, at this time, for sensitive values. You can set the sens values programatically to ensure they are never shown. We will likely add support for secrets (ie sensitive variables) but eta there depends on progress in the community. thanks On Thu, Mar 21, 2019,

sensitive variable values ?

Is there a mechanism in Nifi to use sensitive variable values? For example: would it be possible to store/set password value in StandardRestrictedSSLContextService without exposing it? I am looking for the way to set password in StandardRestrictedSSLContextService from the automated deployment

Re: Automate the Enablement of a StandardHttpContextMap

Also meant to say that it can only be enabled if it is valid, meaning there are no validation messages on the component. So it might be worth checking in the UI to see if there are any validation issues on the service. On Thu, Mar 21, 2019 at 3:02 PM Bryan Bende wrote: > > If you run it with

RE: Automate the Enablement of a StandardHttpContextMap

I'm having a problem with the command you showed below. When I run it for my stuff I get the following: PS C:\Dev\aim\nifi-toolkit-1.9.1\bin> .\cli.bat nifi pg-enable-services -pgid aee943fb-48ac-351e-aef7-29db27d33b0f -p .. \conf\cli.properties ERROR: Error executing command

Re: Automate the Enablement of a StandardHttpContextMap

When a template, or a versioned flow, is instantiated, all the processors are initially stopped and the services are disabled. This is done on purpose since starting and enabling components may cause interactions with external systems, and it may not be clear or desired that just by instantiating

Automate the Enablement of a StandardHttpContextMap

I'm trying to automate the deployment of a template that contains a HandleHttpRequest processor. My issue is that this always comes up with an Invalid component marker after a fresh deployment of the template. The cause of this marker is that the StandardHttpContextMap in the HandleHttpRequest

Re: Problem with property descriptor in InvokeScriptedProcessor

Hi Elemir, Setting the log level to DEBUG outputs more details, it seems the cause of the exception is the following: javax.script.ScriptException: NameError: global name 'StandardValidators' is not defined in

Problem with property descriptor in InvokeScriptedProcessor

Hello, I would like to implement a stateless S3 lister as a python script using InvokeScriptedProcessor in NiFi 1.9.0. I have based my script on the CompressFlowFile processor: