Member since
07-30-2019
3390
Posts
1617
Kudos Received
999
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 228 | 11-05-2025 11:01 AM | |
| 439 | 10-20-2025 06:29 AM | |
| 579 | 10-10-2025 08:03 AM | |
| 394 | 10-08-2025 10:52 AM | |
| 435 | 10-08-2025 10:36 AM |
08-22-2024
02:15 AM
Hi all, I solved sending emails using this configuration: Lorenzo
... View more
08-08-2024
01:04 PM
1 Kudo
@kk-nifi Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
08-06-2024
03:19 PM
@kleyson Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
08-06-2024
06:54 AM
The term "headless" means that "I have access to NIFI server through REST API only!" Anyways, I used below curl to get root level process group: curl --location 'https://localhost:8443/nifi-api/process-groups/root' \ --header 'Authorization: Bearer eyJraWQiOiI1NGU4ZWRkNi00ZTY1LTQ3MmUtYTI5Ni1mNmI3MDJjZDYzNWEiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJkZWVwYWtkb2 I am closing this thread
... View more
08-06-2024
06:35 AM
@MattWho We are using Jndi Configurations, there is no option to pass ssl with jndi configurations.
... View more
08-06-2024
05:33 AM
@CDC- I encourage you to start a new community question rather then adding to an existing question with an accepted answer. Your query is really unrelated to this question. Something appears to be happening to your content prior to even reaching the PutDataBaseRecord processor. I say this because the exception shared indicates the processor is looking for the content in an "archived" content claim. Content claims are only moved to archive once the claimant count is zero (meaning no actively queued FlowFiles are still referencing content on that claim). Any content claims moved to archive are subject to removal/deletion by the background archive clean-up thread. So not surprised the content is missing. The real question here is what is the lineage of this FlowFile and at what point upstream from your putDatabaseRecord processor did the problem develop. Please start a new community question and provide as much detail as possible. Thanks, Matt
... View more
08-05-2024
10:53 AM
@SAMSAL , Thanks for the reply but our current nifi version is 1.23.2 , where it doesn't have that completion strategy. So thinking of implementing executeScript or executeStreamcommand in order to delete the files from SMB after fetchSMB. Please let me know if you have any suggestions for this script , nifi hosted on kube clusters and i've credentials for SMB as well.
... View more
08-05-2024
05:31 AM
HI Matt, thanks for your reply and info shared. We did some changes, so now signing then encrypting the files: signing encrypting When our next system tries to decrypt the file we get this error: gpg: encrypted with unknown algorithm 183 gpg: decryption failed: Invalid cipher algorithm Googling on this, encrypted with unknown algorithm 183, doesn't really give anything usefull. So were trying to figure out, if the issues we're facing is nifi related or on the decrypting side. Any idea's would help. Thank you.
... View more
08-02-2024
08:33 AM
1 Kudo
@Adyant001 The JsonQueryElasticSearch processor does not store state. If the processor has no inbound connection, it will be scheduled to execute its code using the configured properties and scheduling configured. So upon every execution it is going to make the same same query to ElasticSearch. This processor can also be triggered by an inbound FlowFile. So you would have some upstream dataflow to build a query in to its content and that FlowFile is fed to the JsonQueryElasticSearch processor to fetch that specific result. The processor would then not execute again until it received another inbound FlowFile to trigger the execution. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
08-01-2024
06:25 AM
1 Kudo
@Tiger_Name The encrypt-config toolkit was deprecated and removed in the Apache NiFi 2.0.0 release. https://issues.apache.org/jira/browse/NIFI-13414 It was refactored in 2.0.0-M1 (milestone 1) before it was deprecated and removed completely: https://issues.apache.org/jira/browse/NIFI-12243 Your exception sounds like something was not set correctly with regards to the master key in the bootstrap.conf. I'd double check to make sure you set that value correctly. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more