Member since
07-30-2019
3396
Posts
1619
Kudos Received
1001
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 419 | 11-05-2025 11:01 AM | |
| 317 | 11-05-2025 08:01 AM | |
| 456 | 11-04-2025 10:16 AM | |
| 672 | 10-20-2025 06:29 AM | |
| 812 | 10-10-2025 08:03 AM |
05-09-2017
04:05 PM
I literally hit the "tab" key on my keyboard.
... View more
05-24-2017
12:20 PM
@Sunil Neurgaonkar Where the details I provided able to assist you in getting your authorization setup for your users? Can you please mark the answer accepted if it adddressed your original question. Thanks, Matt
... View more
05-05-2017
06:17 PM
@nyakkanti Only processor properties that support the NiFi expression language can be configured to use FlowFile attributes. Some properties (even if the processor property says supports expression language: false, you may be able to use a simple ${<FlowFile-attribute-name>} to return a value from a attribute key/value pair. But this is never true for sensitive properties such as password properties. Password properties are especially difficult since those values are encrypted upon apply. So if you entered ${<FlowFile-attribute-name>} , that is what gets encrypted. The processor then decrypts that when making the connection. Nowhere in that process does it ever retrieve a value from the FlowFile. Thanks,
Matt
... View more
05-08-2017
12:07 PM
@ismail patel Backpressure thresholds are soft limits and some processors do batch processing. The listHDFS processor will produce a list of Files from HDFS and produce a single 0 byte FlowFile for each file in that list. It will then commit all those FlowFiles to the success relationship at once. So if back pressure threshold was set to 5, the ListHDFS processor would still dump all FlowFiles on to it. (even if the listing consisted of 1000s of Files). At that point backpressure would be applied and prevent the listHDFS form running again until the queue dropped back below 5, but this is not the behavior you need here. The RouteOnAttribute processor is one of those processors that works on 1 FlowFile at a time. This allows us to more strictly adhere to the back pressure setting of 5 on its unmatched relationship. The fact that I used a RouteOnAttribute processor is not important, any processor that works on FlowFiles one at a time would work. I picked RouteOnAttribute because it operates off of FlowFile Attributes which live in heap memory which makes processing here very fast. Thanks, Matt
... View more
05-04-2017
06:18 PM
Thanks. Using an external script seems worse in regards to processing time than regex would be and while custom Java processor seems appealing, I don't believe thats the direction we wish to go.
... View more
05-04-2017
04:30 PM
1 Kudo
There is an expression language guide here: https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html For your example you should be able to create an UpdateAttribute processor and add a new property like: myfilename = ${filename:substringAfterLast('/')}
... View more
05-08-2017
03:15 PM
@uttam kumar Where either of the above answers able to resolve your template issue? If you found either helpful, please accept the answer. Thank you, Matt
... View more
05-09-2017
12:45 PM
@Sertac Kaya Glad you were able to get the performance improvement you were looking for by allowing your NiFi instance access to additional system threads. If this answer helped you get to your solution, please mark it as accepted. Thank you, Matt
... View more
05-01-2017
03:16 PM
@Gu Gur And just to add a little detail to Matt's comment, from the documentation, Regular Expressions are entered by adding user-defined properties; the name of the property maps to the Attribute Name into which the result will be placed.
... View more
04-27-2017
02:06 PM
2 Kudos
@Anishkumar Valsalam In a Nifi cluster you need to make sure you have uploaded you new custom component nars to every node in the cluster. I do not recommend adding your custom nars directly to the existing NiFi lib directory. While this works, it can become annoying to manage when you upgrade NiFi versions. NiFi allows you to specify an additional lib directory where you can place your custom nars. Then if you upgrade, the new version can just get pointed at this existing additional lib dir. Adding additional lib directories to your NiFi is as simple adding an additional property to the nifi.properties file. for example: nifi.nar.library.directory.lib1=/nars-custom/lib1
nifi.nar.library.directory.lib2=/nars-custom/lib2 Note: Each prefix must be unique (i.e. - lib1 and lib2 in the above examples). These lib directories must be accessible by the user running your NiFi instance. Thanks, Matt
... View more