In regards to NiFi inside HDF 3.0, this is very stable and brings a lot of new great features. Regarding the new components coming with HDF 3.0 (SAM and Schema Registry), you might want to wait HDF3.1 to start using the components in a production environment (of course it depends what are your requirements). ... View more

Hi @mel mendoza, NiFi is I/O intensive and is requiring dedicated disks. It is not recommended to use the NiFi nodes for something else (at least for a production environment). Besides, for very high rates workflows it is also highly recommended to have dedicated nodes (and disks) for Zookeeper nodes. ... View more

Hi @Julio Cedeno, In nifi.properties, you have two properties for login authentication: nifi.login.identity.provider.configuration.file=./conf/login-identity-providers.xml nifi.security.user.login.identity.provider=ldap-provider The first one points to the file where you are defining your login identity providers. The second one must be the name of the login identity provider you want to use from the definition file. In your file, you must have something like: <loginIdentityProviders> <provider> <identifier>myProvider1</identifier> <class>...</class> <property name="...">...</property> </provider> <provider> <identifier>myProvider2</identifier> <class>...</class> <property name="...">...</property> </provider> <loginIdentityProviders> The error you have is probably due to the fact there is no provider named "ldap-provider" in your configuration file. Are you sure you un-commented the content of the file? Hope this helps. ... View more

You're right, ListenHttp cannot be used as I said... I was thinking about the use of HandleHttpRequest and HandleHttpResponse. With ListenHttp you cannot actually access multiple URLs. An example could be: https://pierrevillard.com/2017/01/31/nifi-and-oauth-2-0-to-request-wordpress-api/ Hope this helps. ... View more

Hi @Simran Kaur, That's not possible. However you can do a single ListenHttp followed by a RouteOnAttribute that will route the flow files based on the requested URL (the attribute should be http.request.url). Hope this helps. ... View more

Hi @Raphaël MARY, Did you set a different value for number of concurrent tasks? Are you in a cluster configuration? ... View more