@Bhushan Babar In order to access the UI of a secured NiFi instance/cluster two things must be successful: 1. A user must be successfully authenticated. By default NiFi will always look for a user's certificate being presented in the connection to use for authentication. If a user certificate is not present, the connection will be closed unless and alternative authentication strategy has been configured in your NiFi. NiFi can be configured to also use LDAP or Kerberos for user authentication. 2. A user must be authorized to access the NiFi resource they are requesting. Only after a user has been successfully authenticated, then the user will be looked up in the configured authorizer to see what NiFi resource that user has been granted access to. In you case, you have a user (cn=neha+ou=business,dc=example,dc=com) that authenticates successfully. I am going to assume this is via user certificate. The full DN from the user certificate is then being passed to the NiFi file based authorizer to determine what resources that authenticated user has been granted. The user added to the authorizer must match this DN exactly. When you changed the DN of the user in the authorizer, it no longer matched what was being presented in the user's certificate and authorized access was being denied. You can always tail the nifi-user.log to see exactly what value is being passed to the authorizer after successful authentication. There will be two entries in this log when a user connects. First you will see a line that says user X successfully authenticated. The next line will say access denied if user was not authorized for the resource. If you want to change the DN in NiFi's authorizer, you must also issue your user a new certificate with a matching DN. Thanks, Matt ... View more

@Huahua Wei 1. Yes, HDF is free (Official Hortonworks support for HDF is what you pay for) https://hortonworks.com/products/data-center/hdf/ 2. As of the most recent official release, HDF and HDP require their own separate Ambari servers. A release coming in the not so distant future will allow you to install one Ambari that can manage both HDP and HDF services. Thanks, Matt ... View more

@Simon Jespersen You need to trigger the PutHiveQL processor only once after ingesting all files? If that is the case, the approach that comes to mind is as follows: Route the success relationship of your ingest processor twice. Route one as you would normally do for your existing dataflow and route the second "success" relationship to a ReplaceText processor. This does not introduce duplicate data or much additional IO. The file content is still only ingested once, but there are two FlowFile pointing at the same content. The "success" relationship that feeds into the ReplaceText processor will be your putHiveQL trigger flow. We are going to use the ReplaceText processor to remove the content of those FlowFiles (down that path only. What happens in the background is new FlowFiles are created at this point, but since they are all zero byte there is little IO involved). Then you can use a MergeContent processor to merge all those 0 byte FlowFiles in to 1 FlowFile. Finally route the "merged" relationship of the MergeContent processor to your PutHiveQl processor. So the Flow would look something like this: The ReplaceText would be configured as follows: and your MergeContent processor would be configured something like this: As always, NiFi provides many ways to accomplish a variety of different dataflow needs. This is just one suggestion. Thanks, Matt ... View more