Member since
07-30-2019
3391
Posts
1618
Kudos Received
1000
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 251 | 11-05-2025 11:01 AM | |
| 157 | 11-05-2025 08:01 AM | |
| 488 | 10-20-2025 06:29 AM | |
| 628 | 10-10-2025 08:03 AM | |
| 402 | 10-08-2025 10:52 AM |
04-09-2024
04:31 AM
1 Kudo
Hi @MattWho 1) Initially, I faced the "NiFi PutSFTP failed to rename dot file issue" only when the child processor was configured with "Outbound Policy = Batch Output". It worked without the child processor group. 2) I modified the PutSFTP failure retry attempt to 3, and it fixed the issue. 3) Later, I introduced a RouteOnAttribute after the FetchHDFS processor for some internal logic implementation, and the PutSFTP error started again. 4) This time, I updated the "Run Schedule" of the PutSFTP processor from 0Sec to 3 Sec, and it again fixed the issue. 5) I have a requirement to transfer stats of each file (with file name, row count, file size) etc. So, I introduced one more PutSFTP processor, and the issue popped up again. 6) Finally, I made the following changes to both of my PutSFTP processors: a) Added PutSFTP failure retry attempt to 3. b) Modified the "Run Schedule" of the first PutSFTP Processor to "7 Sec". c) Modified the "Run Schedule" of the second PutSFTP Processor to "10 Sec". Now it is working fine. Are we getting this issue because of 20 flowfiles processing at a time ? Could you please suggest if this is the right way to fix the "NiFi PutSFTP failed to rename dot file issue"?
... View more
04-08-2024
08:43 AM
@darkcoffeelake 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
04-08-2024
02:09 AM
1 Kudo
@Adhitya, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.
... View more
04-04-2024
05:07 AM
3 Kudos
Connecting Salesforce with Hortonworks Data Flow (powered by Apache NiFi) unlocks powerful data integration. Here's how: NiFi Processors: Utilize processors like "InvokeHTTP" to call Salesforce APIs and retrieve data. Real-Time or Batch: Move data bi-directionally (Salesforce to NiFi or vice versa) in real-time or batches. Data Transformation: Cleanse, transform, and enrich data using NiFi's processors before storing it in your data lake. This salesforce integration helps you leverage valuable Salesforce data for analytics, reporting, and deeper customer insights.
... View more
04-02-2024
09:34 AM
Yes the controller service was working before aks version upgrade
... View more
04-01-2024
06:48 AM
1 Kudo
@ALWOSABY This looks related to the driver version you may be using in the processor. Perhaps trying a different driver version may resolve you issue. Perhaps try ojdbc6 version 11.1.0.7.0? 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
04-01-2024
02:44 AM
1 Kudo
Thanks a lot @MattWho
... View more
03-30-2024
03:33 AM
1 Kudo
I have try something like below which worked. Once Dim1 is completed Dim2:- 1: Attribute to capture StartDate - UpdateAttribute 2: Create Log table in database which will maintain the LastRunTime 3: Custom SQL where updateddate>=$LastRunTime using ExecuteSQL 4: Insert the records in database 5: Update the log file with StartTime attribute from step one1
... View more
03-29-2024
10:23 AM
1 Kudo
@jame1997 Not much to look at from a NiFi side. NiFi is writing to the network successfully and there is some loss then happening between NiFi and your syslog server. Resource usage affecting your NiFi would only slow down processing but not result in dataloss within NiFi. So the PutSyslog would successfully write all bytes to the network before passing the FlowFile to the "success" relationship. Using TCP of course would allow NiFi to confirm successful delivery thus allowing NiFi to appropriately retry, or route to either failure or success relationships. You could look at the data rate NiFi is writing from the putSyslog by looking at the stats on the processor. Then maybe you could experiment with: 1. netstat - nsu to check for UDP packet loss. 2. using a network monitoring tool 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