About justenji

ang_coder · ‎12-08-2020

thank you very much! This works.

justenji · ‎12-06-2020

@dzbeda Try it with: /*:Event/*:System/*:Channel

justenji · ‎10-15-2020

Thanks for your help @ashinde ! I see I was looking at the wrong section of rest-api. OK I have to go on nifi rest-api section flow/history. I will have a look on the nifi.properties but because my report is running every night I suppose the purging doesn't matter. Second option you mentioned concerning when a flow was brought to registry doesn't interest... at the moment.

justenji · ‎09-21-2020

@PVVK It works perfect! Thank you very much.

justenji · ‎02-24-2020

@stevenmatison For the sake of completeness and to confirm your suspicions: With NiFi 1.11.1 parameters also work in the PutEmail-Processor.

justenji · ‎02-24-2020

@MattWho Just for information. This originally described phenomen is solved in the combination NiFi 1.11.1 and NiFi-Registry 0.5.0. A versioncontrolled process-group which contains disabled processors isn't marked anymore with containing "uncommitted changes" after restart of NiFi. Only thing that struck me but isn't a problem: If I disable a versioncontrolled process-group this doesn't lead to marking the process group as having "uncommited changes". But after restart of NiFi this process group is marked as having "uncommited changes". The option "Show local changes" names the differences as "Processor was disabled" for all components within the process group.Now I can proceed a commit and everything stays fine after restart of NiFi.

Slade · ‎02-19-2020

Ok so me and my mate figured it out :). Finally! its like this $.outputs[?(@.name=="EM_CLASSIFICATION")].value

justenji · ‎08-10-2019

Solved Cluster-node users (who obviously execute these actions via rest-api or toolkit cli) had no permission to work with restricted components. Added permission, startet NiFi new and it works. Would by helpfull if somewhere a message would come up to tell that this is an authorization problem...

justenji · ‎07-29-2019

Got it! There was one } missing. Thought if the editor shows the expression coloured it would by syntactical correct. So it has to be: ${RESPONSE:jsonPath('$.[0].id'):equals(${KONTO_BV}): and(${RESPONSE:jsonPath('$.[0].antauschvon'):le(${now():format("yyyyMMdd")}): and(${RESPONSE:jsonPath('$.[0].antauschbis'):ge(${now():format("yyyyMMdd")}): or( ${RESPONSE:jsonPath('$.[0].antauschbis'):isEmpty()})} )} ) }

justenji · ‎06-27-2019

@Shu Oh, so simple... thank you so much!

Online	Offline
Last Visited	‎07-10-2025 07:14 AM

Member Since	‎09-27-2018 05:54 PM
Last Visited	‎07-10-2025 07:14 AM
Posts	138
Kudos received	23

Cloudera Community

Re: How to extract json array using EvaluateJsonPa...

Re: NiFi CLI Tookit : set-param

Re: NiFi InvokeHTTP POST JSON

Re: How to track the Nifi procssors success or err...

Re: [Nifi] - Multiple predicate in recordpath filt...

Re: ConvertJSONtoSQL Issue: How to get unmatched C...

Re: Nifi - Extract value from XML content and add ...

Re: NiFi - REST-API - searching for information ab...

Re: NiFi - JSON seperated date and time - make a t...

Re: NiFi 1.10.0 - PutEmail - Error on using parame...

Re: NiFi - uncommitted changes after restart when ...

Re: How do I extract the attributes from the bel...

Re: NiFi - restricted processors won't start (REST...

Re: NiFi - Expression Language - trouble with nest...

Re: NiFi - JOLT set defaults within an array