Hi everyone, I hope you’re doing well. I am working on a dataflow in Apache NiFi 1.18, and I need to retrieve the queue size information (flowfile count and content size) directly within NiFi itself, not via an external script or Postman. I know that the NiFi REST API provides this data, and I can access it successfully using external tools. However, my goal is to access queue metrics from inside NiFi, for example through processors like InvokeScriptedProcessor, QueryNiFiReportingTask, or any other built-in mechanism, without sending an external REST API request from outside NiFi. Is there a recommended approach, processor, or reporting task that allows NiFi to read its own queue sizes internally? If not, what would be the best practice to achieve this? Any guidance or examples would be greatly appreciated. Thank you in advance!     ... View more

Could someone please help me with this ? Fetch Provenance data using SiteToSiteProvenanceRe... - Cloudera Community - 388418 configuration site to site is not working in http when nifi is running on https ... View more

Hello @RyanCicak  Im trying. this flow but it doesn't work for me. This is my flow What should I do? thanks ... View more

Here u go Open bash script and put the info   url="https://<you environment>:9091/nifi-api/" url_encoded="application/x-www-form-urlencoded" accept_header="Accept: application/json" content_type="Content-Type: application/json" data="username=<your user name>&password=<your password" rm -rf /tmp/a end_point="access/token" curl -k -X POST "${url}${end_point}" -H "${url_encoded}" --data "${data}" > /tmp/a token=`cat /tmp/a` bearer="Authorization: Bearer ${token}"   # Now you are all set to run the curl commands   # Get root id end_point="process-groups/root" curl -k -X GET "${url}${end_point}" -H "${content_type}" -H "${bearer}"   # Get all the components under root which includes all processgroups, process, controller service, connections and everything.    # NOTE: the identifier id WILL NOT MATCH your NIFI id.  They are different.  but this is one stop for full automation end_point="process-groups/root/download" curl -k -X GET "${url}${end_point}" -H "${content_type}" -H "${bearer}" ... View more

writes attribute of some processors (SplitRecord, ReplaceText ) does not contains the error it writes during execution.  How and where to identify the error in that case?  ... View more

@Foivos A The banner is a NiFi core feature and is not tied in anyway to the dataflows you select or build on your canvas. You are correct that the best approach for identifying which dataflows on a single canvas are designated dev, test, or production is through the use of "labels". In a secure NiFi setup, you can use NiFi granular multi-tenancy user authorization to control what components a user can interact with an view. If you use labels, you should set a policy allowing all user to view that specific component, so even if they are not authorized to access the labeled components, they will be able to see why via the label text. Thanks, Matt ... View more

@Sumit Das in my case, the problem was that Hive was not properly configured to support streaming. Basically transactions must be enabled but some others properties must be set as well. More info here: https://community.hortonworks.com/articles/49949/test-7.html The table must also respect some conditions (stored as ORC, transactional, bucketed). ... View more

Thanks @Matt ... View more

Thanks @Matt for confirming. Sorry for not clarifying it better, my use case is to merge flow files that are from the same day, but I've both max and min # of entries set to 100, since I want to merge every 100 incoming flow files into a new merged file, as these files are small, less than 5kb each. So, I'm not trying to merge all flowfiles for the day into just 1 file. ... View more

@Matt, couple of follow up questions on Processor group with multiple input ports; 1) within the processor group, how do you distinguish between flowfiles that are coming from the various input ports. 2) in data provenance screen, is there a way to tell which flowfiles are from which input ports ... View more