@Markus Wilhelm - The documentation states the following: Based on above you should be able to place your core-site.xml and hdfs.site.xml in the NiFi classpath. This will allow all HDFS based processors that do not have a configuration defined for this property to use those as the defaults. - 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

This should be addressed by: https://issues.apache.org/jira/browse/NIFI-5065 ... View more

@philip carey - Ambari has built in variables for server hostnames. So in NiFi configs within Ambari you would configure the property as follows: The above will set the hostname properly to the correct unique hostname in the nifi.properties file on each NiFi node. - The hostname used should always be for a hostname assigned to the server where NiFi is running. - Thanks, Matt - *** Forum tip: Please try to avoid responding to an Answer by starting a new answer. Instead use the "add comment" to respond to en existing answer. There is no guaranteed order to different answers which can make following a response thread difficult especially when multiple people are trying to assist you. ... View more

@neeraj sharma *** Forum tip: Please try to avoid responding to an Answer by starting a new answer. Instead use the "add comment" tp respond to en existing answer. There is no guaranteed order to different answers which can make following a response thread difficult especially when multiple people are trying to assist you. - NiFi Process Groups have no logical binding to a "process". It is just a logical grouping of components on the canvas. Under the hood, NiFi simply has a collection of interconnected components that are being scheduled to execute based on each components configuration. There is no status based on a collection of components completing an operation on a specific FlowFile. So you would need to look at the status of individual processor components. - You may be able to extract the relevant information you are looking for by using the SiteToSiteBulletinReportingTask (get errors when failures occur) and/or SiteToSiteProvenanceReprotingTask (get info based on FlowFile events like create, drop, modify, etc..). - Thanks, Matt ... View more

@SP - I am confused by your statement: "If I create a new template, it is creating a flow.xml.gz and working fine" - A template is not the same thing as a flow.xml.gz file. Are you generating a template, downloading it, and then trying to use that template as a new flow.xml.gz file? If so, that will not work. - Thank you, Matt ... View more

@Sami Ahmad Users who are not authorized for specific NiFi components (process groups, processors, input/output ports, etc...) will only see "ghost" processors. Those ghost processors will not contain any information on the face of them the reveals their type or configuration. - - Unless authorized, user also will not be able to list queues, perform provenance queries, etc on FlowFiles that traverse these components. - There are good reasons why NiFi does not hide these ghost processor completely: 1. All components operate within the same resource constraints of a single JVM. It is important that all user can identify areas of any flow that may be backlogging or have large queues, as these things may impact their own dataflows. While the can not see the actual data or processor details, they can observe FlowFile stat info as you can see in above screenshot. 2. If User1 built a dataflows only user 1 could see, User2 may end up building a dataflow directly on top of it. While functionally NiFi does not care about overlapping components, user3 who logs in and has access to both user1 and user2 flows would. It would make it very hard for user 3 to follow the canvas in such a case. - Thanks, Matt ... View more

@Dan Alan Rather then using --cacerts, trying using the -k option in your curl command. This disables Cleint verificaton of teh server's presented cert. ... View more

@neeraj sharma - Can you elaborate on what "status" information you are looking to retrieve and for which NiFi components? - Thank you, Matt ... View more