@Anishkumar Valsalam I asked around and those quicklinks hostnames are set to the hostnames of the hosts you added to Ambari. You terminal window output above shows you logged into "server1" and not "nifi.server1.com". I could find no way to change them. If you are configuring your nifi.properties file manually, those config changes will be overwritten when you restart NiFi via Ambari. In Ambari, if you configure the nifi.web.https.host= property to a static vale of "nifi.server1.com" , then every node in your NiFi cluster will try to start with that hostname value unless you create a unique config group in Ambari fro each node in your cluster. Wish I could be more help, but it was never the intention of NiFi managed via Ambari to bind to different hostnames then what was provided during your Ambari host registration. I think you only option here is to use config groups, but again that will not change the quicklink URLs. Thanks, Matt ... View more

@Anishkumar Valsalam The Ambari quicklinks URLs are not driven by any of the NiFi configurations. Those quicklinks are driven by the hostname provided when you initially added hosts to your Ambari managed cluster. Since this is not a NiFi configuration issue, I am not sure where to change these quicklink URL values within Ambari. Matt ... View more

@J. D. Bacolod Have you considered using the PutDistributedMapCache and GetDistributedMapCache processors? Have two separate dataflows. One runs on a cron and is responsible for obtaining the token and write that token to the distirbutedMapCache using the putDistirbutedMapCache processor. The Second flow is for doing all your other operations using that token. Just before the invokeHTTP processor add a GetDistibutedMapCache processor that reads the token from the distributed map cache in to a FlowFile attribute. You then use that attribute to pass the token in your connections. One thing to keep in mind is that it is possible that a new token may be retrieved after a FlowFile had already retrieved the old token from the distirbutedMapCache. This would result in auth failure. So you will want your flow to loop back to GetDistributedMapChace processor to get latest key on auth failure on your invokeHTTP processor. This flow does not keep track in any way when a token expires, but if you know how long a token is good for you can set your cron accordingly. Thanks, Matt ... View more

@Anthony Murphy Is this a NiFi cluster or standalone NIFi instance? Make sure that the following property is set to "true" in the nifi.properties file on every instance of NiFi: nifi.flowcontroller.autoResumeState=true If this property is set to false it will trigger all components to come up stopped when Nifi is restarted. Thanks, Matt ... View more

@Alvin Jin My suggestion would be use something like: https://regex101.com/ You can enter your regex and sample test you want to run it against. Matt ... View more

@Kiran Hebbar Hello, Your question is not very clear as to what you are looking for. I am going to assume you are asking how to view the metadata currently associated with a FlowFile passing through your NiFi dataflow(s). There are several ways to view this metadata: Right click on a connection that has queued data and select "List queue" from the context menu. Form the new UI that opens you will se a list of FlowFiles. Click on the icon to the left of any one of the FlowFiles to "view details" of that FlowFile. There you will find a "attributes" tab that list all the key/value pairs associated to this FlowFile. Use data provenance to perform a search on FlowFile events. "Data Provenance" can be found under the upper right corner hamburger menu in the NiFi UI. Click the search icon to open a "Search Events" UI where you can add criteria to limit the results (Provenance returns 1000 of the most recent events). From the final list use the same "view details" icon to the left of an event to open a new UI that will show the Attributes of your selected FlowFile. Use the LogAttribute processor. Add this processor anywhere in your dataflow. As FlowFile pass through this processor their FlowFile Attributes as they exist at the time of passing through this processor will be logged to the nifi-app.log. Keep in mind that this processor can greatly increase the size of your logs and require more space to store your logs. If you found this answer addressed your question, please mark it as accepted. Thanks, Matt ... View more