About felicien_cathe1

felicien_cathe1 · ‎11-21-2018

Thanks for your answer, I wanted to have only "one" queue were all flowfiles would be waiting.I know now that it was i bad idea => I reduced the size of the queue and now use backpresure. It corrected the priority problem. Thanks again !

felicien_cathe1 · ‎11-13-2018

Thanks Matt for this very clear article I'm using a priorityAttributePrioritizer for my queues and it seems that is not taken in account when the flowfile is not in the active queue. (The queue size is 50000, and when a flowfile with a better priorityAttribute than all flowfiles in the queue arrives, it is only processed when it arrives in the active queue) Is this the expected behaviour ? I was expecting that the flowfile with a better priority will be processed first no matter the number of flowfiles in the queue

felicien_cathe1 · ‎04-05-2018

If anyone needs it (Matt answers helped me a lot but is not exactly correct) : for(var prop in context.properties) { if(prop.isDynamic()) { var name = prop.getName(); var value = context.getProperty(name).evaluateAttributeExpressions(flowFile).getValue(); //or var value = context.getProperty(name).getValue(); if AttributeExpression are not needed log.info('name : ' + name + " value : " + value); } }

felicien_cathe1 · ‎04-05-2018

Thanks a lot ! , i'll have a look to JsonSlurper and JsonOutput

felicien_cathe1 · ‎04-05-2018

@Matt Burgess

felicien_cathe1 · ‎04-03-2018

This is working perfectly with this groovy script. However, I wanted to do that in Javascript (since I want to manipulate JSON objects), is there an easy way to filter the dynamics properties ? For now, I can retrieve the list of properties (in context.properties), but I don't see any difference between the "hard coded properties" ("script engine","script file", "modules directory") and the properties I added myself. Thanks in advance if you can help

felicien_cathe1 · ‎04-03-2018

Not really.. but Matt's answer is what I needed, thank for your answer anyway !

felicien_cathe1 · ‎04-03-2018

Thanks Matt ! This is exactly what I needed

felicien_cathe1 · ‎03-30-2018

Hi, I am trying to make a Javascript code for the executeScript processor and I wonder if it's possible to get the name of a custom property added from the executeSript Properties tab. I know that if I add a property "myProperty", I can access it from the script by using myProperty.getValue() (or with .evaluateAttributeExpressions() when needed). But is it possible to find the key "myProperty" from inside the script ? I would like to do something like for(i = 0 ; i < customProperties.length ; i++){ propertyName = customProperties[i].getName() value = propertyName.getValue() //Do something with propertyName and its value } Thanks in advance ! Félicien

Online	Offline
Last Visited	‎01-14-2019 05:15 PM

Member Since	‎06-28-2017 09:07 AM
Last Visited	‎01-14-2019 05:15 PM
Posts	9

Cloudera Community

Cloudera Community

Re: Dissecting the NiFi "connection"... Heap usage...

Re: Dissecting the NiFi "connection"... Heap usage...

Re: Get dynamic property name in execute script

Re: Get dynamic property name in execute script

Re: Get dynamic property name in execute script

Re: Get dynamic property name in execute script

Re: Get dynamic property name in execute script

Re: Get dynamic property name in execute script

Get dynamic property name in execute script