Hello @Hasib1971,  Are you still facing an issue or that was what solved your error?  If you still have an issue, please open a new thread so we can help you there.  ... View more

Hello @IgorSpryzhkov,  Let me see if I can help with your questions:  1. How to get list of Process Groups in the root and in Each PG? For this, you may be able to get the information with this API:  GET /process-groups/{id}/process-groups https://nifi.apache.org/docs/nifi-docs/rest-api/index.html    2. How to get list of Processors in Each PG?   For this one, this other API request may get you the info:  GET /process-groups/{id}/processors   3. How to organize in Groovy cycles for scan PGs? In NiFi ExecuteScript (Groovy), you can call the API recursively.  So you should be able order the logic there to fit what you need.    4. How to save / read data in/from Groovy dictionary /  NiFi cache? You can use any of these options: - DistributedMapCache (preferred if cluster, can use processors such as PutDistributedMapCache and FetchDistributedMapCache). - File-based persistence (write JSON file to disk). - FlowFile attributes (if just passing data). ... View more

@FGhidotti I have reached out via DM with further steps, thank you! ... View more

Hello @HoangNguyen,  The difference I see is that your queries does not match.  During all the queries I see this:  ,e.tsn as ticketserialnumber But on the SQL after the "/* Start Here */" it is different:  ,e.tsn as tsn On this type of queries you should always match the order and types.  ... View more

Hello @Chetan_mn,  I was checking and the entrypoint for this kind of scenarios should be start.sh, that should call everything you need to start it.  https://hub.docker.com/layers/apache/nifi/2.4.0/images/sha256-e8ca069f1533e6ee52d706fa3395ea16fe6f29468c7c6234a3f1c6232b912704 Do you have any error log that can give us more clues here?  ... View more

Hello @Alf015,  I found two thing that may be causing this issue.  First, the "vault.namespace" should not have the "/" at the end:  https://docs.spring.io/spring-vault/docs/2.3.x/reference/html/#vault.core.environment-vault-configuration On the Paramenter Provider, "key value path" should be only "secret", all the rest is taken from the header.  https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hashicorp-vault-nar/1.28.0/org.apache.nifi.vault.hashicorp.HashiCorpVaultParameterProvider/  Try those changes and let us know if this fails.  If it does, maybe the Debug level for those modules can provide more information:  <logger name="org.apache.nifi.vault" level="DEBUG"/> <logger name="org.apache.nifi.parameter" level="DEBUG"/> <logger name="org.springframework.vault" level="DEBUG"/> ... View more

I know this is old topic, but do you have solution applied on this so it can be shared with the community @phr1 ?  ... View more

Hello @hus,  Directly the ExecuteSQL processor does not support binding.  The input should be directly SQL query.  https://nifi.apache.org/components/org.apache.nifi.processors.standard.ExecuteSQL/ But, according to the API docs, the processor can be started via a FlowFile:  https://javadoc.io/static/org.apache.nifi/nifi-standard-processors/2.4.0/org/apache/nifi/processors/standard/ExecuteSQL.html  So technically you should be able to start this query by using ReplaceText to inject values dynamically, for example.  ... View more

@zzzz77  Provenance can be very noisy depending on size of your dataflows and the amount of FlowFIles being processed through those dataflows.  The provenance repo has age and size configuration that trigger roll-off of old events.   So you may not reach the retention age if you reach size first.  Also would not be trying to read provenance files while they are being written to.    The SiteToSiteProvenanceReportingTask might be the solution you are looking for in Apache NiFi.   This reporting task will send all provenance events over Site-To-Site protocol to a target NiFi where you can then feed them into any long term storage medium of your choice in a human readable format.   Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Hello @SalimAlhajri,  The Transparent Authentication is built-in Cloudera AI.  When the application is started, it will inject the REMOTE-USER and REMOTE-USER-PERM HTTP headers automatically, this is why it is transparent, no manual intervention is needed.  https://docs.cloudera.com/machine-learning/1.5.5/applications/topics/ml-securing-applications.html  ... View more