@domR    i) Do List processors w/ timestamp tracking store state locally? --- If you are running a standalone NiFi and not a NiFi cluster, all state will be stored locally on disk. --- If clustered, this depends on the list processor and how it is configured.  The ListFile processor can be configured to store state locally or remotely depending on your use case.  For example a ListFile is added to a NiFi cluster and every node is listing from a local path not shared across all nodes, you would want each node to store the listFile state locally since it would be unique per node and other nodes have no access to the directory one each node.  If your listFile is listing against a mounted directory that is mounted to every node in the cluster, the listFile should be configured for remote and configured t run on primary node only. --- Other list based processors all store state locally ONLY when it is a standalone NiFi.  Clustered NiFi installs will trigger store to be stored in zookeeper. ii) Does this state survive NiFi restarts? --- Yes, local state is stored on disk in NiFI's local state directory.  Cluster/Remote state is store in zookeeper.  State configurable is handled by the state-management.xml configuration file.   iii) If running on primary node only, would this mean when another primary node is chosen, the List processor would list any files it hasn't tracked (and re-ingress a large backlog of files if still there)? --- When a primary node change occurs, the primary node only processors on the previous primary node are asked to stop executing and the same processors on the newly elected primary node are asked to start.  On the new node, that processor will retrieve that last known state stored in zookeeper for that component before executing.  There is a small chance for some limited data duplication.  When old elected primary node processors are asked to stop that does not kill active threads. If the processor is in the middle of execution and does not complete (update cluster state in ZK) before newly elected primary node pulls cluster state when it starts to execute, some files may be listed again by newly elected node, but it will not list from beginning. iv) What out-of-box solutions can help to get around the issue of non-persisted non-distributed listing, or do we need custom auditing triggering individual listings? ---  NiFi does persist state through node restarts.   Note; You can right click on a processor that stores state and select "view state" to see what has been stored. You can also right click on a processor and select "view usage" to open the embedded documentation for that component. The embedded documentation will contain a "State Management:" section that will tell you if the component stores state and if that state is stored locally or cluster (ZK).   Hope this helps, Matt ... View more

@Alexandros    Going to ask the simple question first... There are FlowFiles traversing the processors in this newly instantiated flow from your template, correct? --- The next thought would then be around authorizations (assuming your NiFi is secured)  1. Is your user running the provenance query authorized to "view provenance" and "view the data" on the components?  If these are set on the process group containing these processor components and not set on the components themselves, the components will inherit the polices from the process group. 2. Is this a NiFi cluster?  If so, make sure your NiFi nodes are also authorized to "view provenance" and "view the data".  When you authenticate in to NiFi and run a provenance query, that query is replicated to all nodes in your cluster.  Those query results are then returned to the node on which the originating request was made.  If that node is not authorized to view data returned from other nodes, it will not display.   --- Then we need to make sure provenance it still working: While you are seeing provenance events displayed for your existing flow, are those returns recent?  If you monitor the contents of your provenance_repository, do you see timestamps updating on the <num>.prov files?  Need to make sure provenance has not stopped working for some reason.  Also make sure you are using the WriteAheadProvenanceRepository implementation (should be default in 1.11) and not the PersistentProvenanceRepository implementation (configured in nifi.properties file).   Hope this helps, Matt ... View more

@Gubbi  Depending on which processor is being used to create your FlowFile from you source linux directory, you will likely have an "absolute.path" FlowFile attribute created on the FlowFile. absolute.path = /users/abc/20200312/gtry/   You can pass that FlowFile to an UpdateAttribute processor which can use NiFi Expression Language (EL) to extract the date from that absolute path in to a new FlowFile attribute Add new property (property name becomes new FlowFile attribute): Property:          Value: pathDate          ${absolute.path:getDelimitedField('4','/')}   The resulting FlowFile will have a new attribute: pathDate = 20200312 Now you can use that FlowFile attribute later when writing to your target directory in S3. I assume you would use the putS3Object processor for this? If so, you can configure the "Object Key" property with the following: /Users/datastore/${pathDate}/${filename}   NiFi EL will replace ${pathDate} with "20200312" and ${filename} will be replaced with "gyyy.csv".   Hope this helps you, Matt ... View more