@Amit_barnwal 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

another interesting point is how to implement on updateattribute the function of checking whether it was delivered to puthdfs because if hdfs runs out locally, the process continues to go and the files are not written but are thrown out of the queue and go to another file in the basket, in fact, files are lost if the meso runs out and the chain does not stop , you need to check if the file in ndfs did not arrive stop the stream or the memory ran out in ndfs stop putndfs and let the recycle bin fill up ... View more

@cotopaul, Thank you a lot. That is exactly what I need.   ... View more

Hello @MattWho @SAMSAL @steven-matison @DigitalPlumber @cotopaul , after confirming the access I'm able to verified I can access the bucket from aws cli on the same system Nifi is running on and download files.  The problem I'm having now is that the ListS3 pickup the list of the files from the bucket but the FetchS3 doesn't do anything.  When I enabled debugging on the FetchS3 I receiving the following error message.    FetchS3 Error message    FetchS3 Configuration ListS3 Configuration  Any suggestion to what is causing the issue?   ... View more

Hi, Can you answer this question please How to do Dynamic property naming in NIfi? - Cloudera Community - 369374 ... View more

The file can be found within your NiFi logs folder, where you have your other logs as well. ... View more

hi @ushasri,   The file you are looking for is called flow.xml.gz and can be found on each NiFi node, within the conf folder.   More information can be found here: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html flow.xml.gz: Everything the DFM puts onto the NiFi User Interface canvas is written, in real time, to one file called the flow.xml.gz. This file is located in the nifi/conf directory by default. Any change made on the canvas is automatically saved to this file, without the user needing to click a "Save" button. In addition, NiFi automatically creates a backup copy of this file in the archive directory when it is updated. You can use these archived files to rollback flow configuration. To do so, stop NiFi, replace flow.xml.gz with a desired backup copy, then restart NiFi. In a clustered environment, stop the entire NiFi cluster, replace the flow.xml.gz of one of nodes, and restart the node. Remove flow.xml.gz from other nodes. Once you confirmed the node starts up as a one-node cluster, start the other nodes. The replaced flow configuration will be synchronized across the cluster. The name and location of flow.xml.gz, and auto archive behavior are configurable. See the System Administrator’s Guide for further details. ... View more

thanks for the reply cotopaul.  I'm still very new to NiFi clusters and was thinking, from a purely cloud architecture perspective, that it typically makes sense to abstract the specific endpoints from the end user.  I'll review the url you provided.  Thanks again for your reply. ... View more