@Jayson Ramey - The NiFi Registry does not have a separate nifi-registry-user.log. All user access events are logged in the nifi-registry-app.log. - Sounds like the issue was identified as a old browser version problem. Did you try using the developer tools built in to your browser as suggested by @Bryan Bende to see if you were encountering any java script errors? - Sounds like the solution here requires the upgrading of your browser versions. - Thank you, Matt ... View more

@Dan Alan - Anything you can do via the UI, you should be able to accomplish using NiFi's rest-api. https://nifi.apache.org/docs/nifi-docs/rest-api/index.html - The easiest way to learn what specific rest-api call you need to make to accomplish a task is through using the developer tools in your browser. Perform the action via the UI and then via developer tolls save off that action as a curl command. - for example (assume secured NiFi using a login provider): obtain authentication token: token=$(curl -k 'https://<nifi-node>:9091/nifi-api/access/token' --data 'username=<username>&password=<password>’) - Then use that token to stop a specific processor by processor UUID: curl 'https://<nifi-node>:9091/nifi-api/processors/aab961c3-6bcd-18e7-0000-00001d74d4ea' -X PUT -H "Authorization: Bearer $token" -H 'Content-Type: application/json' -H 'Accept: application/json, text/javascript, */*; q=0.01' --data-binary '{"revision":{"clientId":"248a328f-a133-1cd0-18c1-8997e36ef898","version":1},"component":{"id":"aab961c3-6bcd-18e7-0000-00001d74d4ea","state":"STOPPED"}}' --compressed --insecure - Thank you, Matt - When an "Answer" addresses/solves your question, please select "Accept" beneath that answer. This encourages user participation in this forum. ... View more

@Vladislav Shcherbakov - The FetchFTP processor is designed to retrieve a single File per execution. The data returned is added as content to the FlowFile that was used to trigger the execution. You cannot use a regular expression that will return more then one target file. So wildcards are not going to be supported here. - The FetchFTP processor is most commonly used in conjunction with the listFTP processor. The ListFTP processor connects to the target FTP server to retrieve a listing of all Files (based on processor filter configurations). The output of this processor will be a unique 0 byte FlowFile which contains a number of FlowFile Attributes which can then be used by the FetchFTP processor to retrieve the actual content. - This two phase approach has to purposes: 1. The ListFTP processor maintains state so the same files are not listed more then once. This allows you to leave the target files in the source directory without them being consumed by FetchFTP processor more then once. 2. This setup allows you to spread the load of pulling large amounts of data from FTP across multiple nodes in a NiFI cluster. ----- ListFTP processor would be configured to execute on Primary Node only. ----- ListFTP feeds 0 byte FlowFiles to an Remote Process Group (RPG) that is used to redistirbute those 0 byte FlowFiles to all the nodes in your NiFi cluster. ----- The FetchFTP processor would then be configured to execute on all nodes in your cluster, so every node does work retrieving different files and performing follow-on NiFi processor work on them. - Thank you, Matt - When an "Answer" addresses/solves your question, please select "Accept" beneath that answer. This encourages user participation in this forum. ... View more

@Rangareddy Y - NiFi does not support dynamic property creation from an XML based input file. Some properties on some processors will support NiFi's Expression Language (EL) which would allow supporting properties to retrieve a defined variables value. Those key/value variables can be defined in a number of places: 1. On the incoming FlowFiles to that NiFI processor in the form of FlowFile Attributes. 2. On the NiFi Process Group that contains your processors 3. From a NiFi variable registry file. (key/value property file. Cannot be updated in real time. changes to this file would require a NiFi restart) 4. NiFI JVM properties defined in NiFi's bootstrap.conf file (Restart required each time this file is edited) 5. NiFI process owner's environment variables (Restart of NiFi Required if user env variables are edited/added) - None of NiFi's processors will support the use of EL to define processor sensitive property values like passwords. Floating over the small "question mark" icon to the right of a property name in a processor will indicate if the use fo EL is supported by that processor configuration property. - Referenced documentation on NiFi's EL: https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#custom_properties - Thank you, Matt - When an "Answer" addresses/solves your question, please select "Accept" beneath that answer. This encourages user participation in this forum. ... View more