Member since
07-30-2019
3471
Posts
1642
Kudos Received
1020
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 148 | 06-03-2026 06:06 PM | |
| 460 | 05-06-2026 09:16 AM | |
| 826 | 05-04-2026 05:20 AM | |
| 495 | 05-01-2026 10:15 AM | |
| 621 | 03-23-2026 05:44 AM |
12-23-2019
10:24 AM
@Former Member Simply configuring the ldap-provider in the identity-providers.xml file will not result in NiFi-Registry using it. Make sure you have set the following property in the nifi-registry.properties file: nifi.registry.security.identity.provider=ldap-provider This tells NiFi to use the "ldap-provider" configured in that file. Also make sure the file is named "identity-providers.xml" and not "login-identity-providers.xml". NiFi-Registry uses the former while NiFi uses the latter identity providers filename. One other things to consider... If NiFi-Registry is configured to support Spnego: nifi.registry.kerberos.spnego.authentication.expiration=12 hours
nifi.registry.kerberos.spnego.keytab.location=
nifi.registry.kerberos.spnego.principal= Spnego auth will be attempted before any configured identity provider. So all it takes is to have Spnego enabled in your browser and NiFi-Registry to be setup to support Spnego auth and you will not see login page as well. If you do not have Spnego enabled in your browser, then this is not your issue because even if configured if browser does not return Spengo creds, NiFi-Registry will move on to next configured authentication provider. Hope this helps, Matt
... View more
12-23-2019
09:48 AM
@Boenu You will need to configure your HandleHttpRequest processor with a SSL Context Service in order to encrypt data in transit being sent to this processor from a client. This of course then means you client needs to be able to at a minimum to trust the server certificate presented by this SSL context service in the TLS handshake. The truststore you use in the NiFi SSL Context Service will only need to contain the public cert for your client or complete certificate trust chain for your client if you have configured your HandleHttpRequest processor to "Need authentication" in the Client Authentication property. Mutual Authentication is not needed to ensure encryption of data in transit. Hope this helps, Matt
... View more
12-18-2019
04:41 PM
@girish6 Anything you can do via the NiFi UI, can also be done using the NiFi Rest-api. Using the developer tools available ion most browsers is a great way to learn how the rest-api calls work. You can have the developer tools UI open while you perform similar actions on the canvas and then capture those rest-api request directly from the developer tools (most offer an option to "save as curl"). It can be challenging to build dataflows via the UI in terms of placement. While NiFi does not care if all your components are stacked upon one another at position 0,0, if you ever try to access the UI to modify a component that way later it would be nearly impossible as it would be one blob in the center of the canvas. You can find the rest-api docs embedded in your NiFi installation by going to the Global Menu in the upper right corner of your NiFi UI and selecting Help. Hope this helps, Matt
... View more
12-17-2019
07:04 AM
@saciya I am not sure why this is not working for you. I built a test flow and it is working fine for me. Here is how I have my ReplaceText processor component configured: I also used "shift+enter" to create a new line at the end of the header being inserted (note that a blank line "2" is shown) and the "Prepend" replacement strategy. I passed it the following test CSV content: 15-Dec-19,Baltimore,27
17-Dec-19,Baltimore,34 I then listed the queue on the success relationship connection outbound from the ReplaceText processor. From there I could click on "View Details" icon to far left of my FlowFile in the queue list and then click "VIEW' to see what the resulting content looked like. Here is what I see for my sample source content above: I am using Apache NiFi 1.9 Hope this helps, Matt
... View more
12-17-2019
06:30 AM
@PavelPrudnikov The specific error you are seeing in the bulletin produced on your PutDatabaseRecord processor is telling you that the processor is not able to find the schema you have configured in your CSVReader. Did you define a schema in one of the Schema Registry providers? Is the value assigned to the "schema.name" FlowFile Attribute on your inbound FlowFile an exact string match with the schema name in your Schema Registry provider? It may be helpful if you share a screenshot of the FlowFile attributes on your FlowFile in the queue to the putDatabaseRecord processor and share your CSVReader configuration as well. Have you tried just using the infer-schema option in the CSVReader Schema Access Strategy? Hope this helps, Matt
... View more
12-16-2019
11:48 AM
@JSJ Let's assume you have following directory structure: /nifi/test/AX1/ /nifi/test/AX2/ /nifi/test/XY1/ /nifi/test/XY2/ You would configure your listFile processor as follows: Hope this helps, Matt
... View more
12-13-2019
07:02 AM
@fowler7878 You are correct that MonitorActivity can not be used to monitor on activity based on per month thresholds. Your use case is not one NiFi is designed to handle. NiFi is designed to work with FlowFiles and typically NiFi processor are not designed to return directory listings. Your use case may require you to build your own custom NiFi processor or perhaps your own custom script that your can execute via ExecuteStreamCommand or ExecuteScript processors where the script returns number of files in a target directory which you can then make notification routing decisions with. I was just trying to offers a builtin solution/suggestion while not exactly what you are looking for. Thank you, Matt
... View more
12-13-2019
06:51 AM
@Love-Nifi Just wanted to add that as @jsensharma mentioned, NiFi will enforce TLS 1.2 as of Apache NiFi release version 1.2.0 but only for all inbound connections to NiFi. NiFi can still support negotiating lower TLS version when making outbound connections in order to support older destination systems. Those processor would use a sslContextService which can be configured to restrict what TLS version is used/allowed.
... View more
12-13-2019
06:46 AM
@varun_rathinam The only method offered by the MergeContent Processor to force a bin to merge when it has not reached the configured minimum set values is the "Max Bin Age" property. How long does it take to accumulate 500 FlowFiles in a bin for merge? Set your Max Bin age to a value higher than that time duration. Now to avoid merging FlowFile from day 1 and day 2 (scenario where day 2 files start showing up at your MergeContent processor before end of day 1 max bin age time has been reached), I suggest using the "Correlation Attribute Name" to make sure only FlowFiles from the same day are placed in the same bin. This would require you to extract the date/day from your FlowFiles somehow (maybe by HDFS dir path, or filename, or some file metadata if these exist). Hope this helps, Matt
... View more
12-13-2019
06:37 AM
1 Kudo
@Biswa NiFi's Expression Language (EL) will not support wildcard in attribute subject names. I suggest you pull height and width in to a set of standardized attribute names: Use the UpdateAttribute processor advanced UI to create some rules. Fore example: if "PNG-IHDR.Image Height" attribute exists, create new attribute "image height" with value from "PNG-IHDR.Image Height" Do the same for the other 3 unique attribute names, thus resulting in a static attribute subject names for height and width for use later in your flow for comparison/routing decisions. Hope this helps, Matt
... View more