Member since
08-08-2024
108
Posts
27
Kudos Received
10
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 416 | 04-15-2026 11:56 AM | |
| 996 | 04-07-2026 02:00 PM | |
| 434 | 03-12-2026 09:53 AM | |
| 457 | 03-04-2026 03:07 PM | |
| 652 | 02-10-2026 07:31 PM |
02-14-2026
09:45 AM
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
02-13-2026
09:53 AM
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
02-13-2026
06:50 AM
Hello @FGhidotti, You should be able to update it under the Cloudera SSO. That is accesible from any Cloudera page, under your user icon. If that does not work, you may need to open an administrative case to get the user updated.
... View more
02-12-2026
03:07 PM
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
02-12-2026
02:38 PM
1 Kudo
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
02-12-2026
08:41 AM
1 Kudo
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
02-10-2026
07:43 PM
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
02-10-2026
07:39 PM
1 Kudo
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
02-10-2026
07:31 PM
Hello @jI-mi, That CML version is kind of old. If I'm not wrong, that version comes with DS 1.5.2. There the only supported versions for CUDA where 11.4 and 11.1, so you will not be able to do that. https://docs-archive.cloudera.com/machine-learning/1.5.2/runtimes/topics/ml-runtimes-nvidia-gpu.html And actually, even the most recent versions only support CUDA 12.5.1 Due to Tensorflow requirements, looks like CUDA 12.8 is not planned to be supported. You can check with your Cloudera Account Team to request this feature providing your business needs.
... View more
02-09-2026
07:41 PM
Hello @jI-mi, Thanks for being part of our community. Can you please explain your question a little bit more? Also, can you please tell us your CML version? I was quickly checking on CML 1.5.5 and the CUDA 12.8 is not listed as supported, so this may also give you some hints: https://docs.cloudera.com/machine-learning/cloud/runtimes/topics/ml-runtimes-nvidia-gpu.html
... View more