Member since
07-30-2019
3436
Posts
1633
Kudos Received
1012
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 159 | 01-27-2026 12:46 PM | |
| 575 | 01-13-2026 11:14 AM | |
| 1276 | 01-09-2026 06:58 AM | |
| 1040 | 12-17-2025 05:55 AM | |
| 506 | 12-17-2025 05:34 AM |
02-10-2020
07:14 AM
Thanks Matt. Where the flow file will be created to give to fetch processor. In my scenario , avro files will be created in subdirectories. I saw listhdfs supports hdfs.But i am not able to connect the listhdfs processor to fetch processor
... View more
02-10-2020
01:21 AM
@MattWho Thanks for the answers ! You're right in my nifi.properties : nifi.security.needClientAuth is set to false. My version of nifi is an old one (1.9.2). I will pay more attention during my next upgrade. My nifi and my nifi-registry are both secured. I have only added the CN of my nifi app cert into authorizers.xml file (userGroupProvider and accessPolicyProvider).
... View more
02-07-2020
08:23 AM
@nishank_paras Let's assume your input FlowFile content looks like this: Date, IP, Description
01-30-2020, 10.0.0.1, server1
01-30-2020, 10.0.1.2, server2
01-30-2020, 10.0.3.4, server3
01-30-2020, 10.0.4.6, server4
01-30-2020, 10.0.10.2, server5 You would configure your ReplaceText processor as follows: The Search Value contains a java regular expression which will match on your entire line and uses one capture group. The Replacement Value says to replace everything matched by the Search Value Regex with only the value from capture group 1. We then configure ReplaceText to evaluate that Regex against each line. The resulting FlowFile output to the success relationship will have content that looks like this: IP
10.0.0.1
10.0.1.2
10.0.3.4
10.0.4.6
10.0.10.2 Hope this helps, Matt
... View more
02-06-2020
07:41 AM
@Kielbik You can stop version control on your Process Group in NiFi and then start version control again to recreate the flow in nifi-registry. NiFi and NiFi-registry do not offer an undo action when you inadvertently delete an item. Hope this helps, Matt
... View more
02-05-2020
08:00 AM
Want to add some clarity to this last comment: ListenHTTP requires 2-way TLS when enabled if a SSLContextService has been configured with a truststore. The truststore is used to trust the client certificate presented by the client, for the purpose of authentication, connecting to this secured ListenHTTP processor. If only a keystore and no truststore is configured in the SSLContext service, the ListenHTTP will not require that clients present a client certificate. The server certificate from the keystore will be presented to the client so the client can verify that it trusts the server (NiFI listenHTTP jetty server) that it is connecting with.
... View more
02-04-2020
08:34 PM
Thanks a lot Matt!!
... View more
02-04-2020
09:52 AM
@lueenavarro Using a key that has no password protection is bad security. This is why the processor requires a password to protect that key. Adding a password to the key you were provided does not alter the key nor does it require you to obtain a new key in order to add a password. Only other option i can suggest is to use an ExecuteStreamCommand or ExecuteScript processor to to execute the SFTP command with your password-less key to put content to your SFTP server. Hope this helps, Matt
... View more
01-30-2020
05:45 AM
Thanks for reaching out to me. It was my mistake , I was redirecting/connecting the wrong out port to pg2_in. It's resolved now
... View more
01-27-2020
01:55 PM
@VijaySankar Unfortunately with the information you have shared, it is not possible for me to validate what the issue is here. I would need to output from the openssl commands i shared earlier to help. openssl s_client -connect <server hostname>:<server port> Also the verbose listing of both your keystore and truststore files would be needed: keytool -v -list -keystore keystore.jks
keytool -v -list -keystore nifi.com.jks The target server is what decides if connection is going to use mutual auth or not. The invokeHTTP is the client side of this connection and only provides what the server asks for in the server hello response. It is possible also in that server hello response that the server wants a client certificate; however, the list of CAs sent in that server hello response does not contain a CA capable of trusting your clientAuth PrivateKeyEntry in your nifi.com.jks. In that case client would not send the client certificate since server is incapable of trusting it. Matt
... View more
01-23-2020
11:51 AM
Will do. Thanks.
... View more