Member since
07-28-2025
6
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 941 | 07-28-2025 08:15 AM |
04-20-2026
08:09 AM
1 Kudo
Hi, I had to downgrade and upgrade all my nars to 2.0.0 for it to work.
... View more
04-09-2026
07:57 AM
Hello @vafs, I see how my earlier explanation may have been confusing, so I’ll focus firstspecifically on the current tests. We ran two separate flows: Flow with Debezium NAR + two Azure NARs This resulted in the errors previously shared in this topic, affecting both the CDC processor and the PutAzureEventHub processor. Flow with only the Azure NARs This flow simply generates text and sends it to Event Hub. However, it also fails with the same “not a valid processor type” error for the PutAzureEventHub processor. So, even without the Debezium 1.x NAR, we are still encountering the same issue with the Azure processor.
... View more
04-08-2026
07:09 AM
Hello @vafs, Thank you for your reply. I attempted to test the same Debezium NAR with a more recent version, however, we were unable to upload new extensions to EFM. I understand your point regarding the use of an older Debezium NAR version. However, we also conducted tests using a separate class and flow that included only the two Azure NARs (both are above 2.3 in versions) without the debezium processer & nar (About a year ago, this same flow and exact NARs worked with the exact same MiNiFi image currently tested). For this reason, I believe the issue may not be solely related to the Debezium 1.x NAR, as the EventHub processor is also affected.
... View more
04-06-2026
04:19 AM
Hello Everyone, We are currently conducting tests to read data from CDC Debezium-enabled postgreSQL database and write to Azure EventHub. Actions performed: We uploaded three NARs needed to use the put We added the following NARs as extensions: nifi-azure-nar-2.4.0.nar nifi-azure-services-api-nar-2.3.0.nar nifi-cdf-debezium-postgresql-nar-1.28.1.2.1.7.2006-1.nar After a manifest refresh in EFM, we were able to see and use the PutAzureEventHub and CaptureChangeDebeziumPostgreSQLprocessor processors. We then configured the flow, published a new version, and confirmed that the flow was successfully pushed to MiNiFi. Issue The Flow is pushed to MiNiFi but it is not being validated, thus the publish request fails, we have errors as if the newly added processors are not recognized, I believe? 2026-04-02 12:22:09,379 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.379 [Validate Components Thread-3] DEBUG org.apache.nifi.controller.AbstractComponentNode -- Computed validation errors with Validation Context StandardValidationContext[componentId=9706f422-72e7-4ee9-b7e5-525fab338432, properties={}]; results = ['Missing Processor' validated against 'Any Property' is invalid because Processor is of type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub, but this is not a valid Processor type] However, In the logs it seems the NARs have been unpacked and we can see the unpacked files. I tested deploying a flow that uses only the default MiNiFi processors. The flow validated successfully, and MiNiFi started without any issues. Below are curated entries from the minifi-bootstrap.log file related to the added NARs: 2026-04-02 12:22:09,133 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.133 [pool-15-thread-1] DEBUG org.apache.nifi.controller.serialization.VersionedFlowSynchronizer -- Could not find a compatible bundle for org.apache.nifi:nifi-azure-nar:2.4.0 type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub
2026-04-02 12:22:09,133 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.133 [pool-15-thread-1] DEBUG org.apache.nifi.controller.serialization.VersionedFlowSynchronizer -- Could not find a compatible bundle for com.cloudera:nifi-cdf-debezium-postgresql-nar:1.28.1.2.1.7.2006-1 type com.cloudera.nifi.processors.debezium.CaptureChangeDebeziumPostgreSQL
2026-04-02 12:22:09,148 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.148 [pool-15-thread-1] WARN org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer -- Unknown bundle com.cloudera:nifi-cdf-debezium-postgresql-nar:1.28.1.2.1.7.2006-1 for processor type com.cloudera.nifi.processors.debezium.CaptureChangeDebeziumPostgreSQL - will use Ghosted component instead
2026-04-02 12:22:09,148 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.148 [pool-15-thread-1] WARN org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer -- Unknown bundle org.apache.nifi:nifi-azure-nar:2.4.0 for processor type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub - will use Ghosted component instead
2026-04-02 12:22:09,367 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.367 [pool-15-thread-1] DEBUG org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer -- Adding Processor with ID 9706f422-72e7-4ee9-b7e5-525fab338432 of type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub
2026-04-02 12:22:09,367 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.367 [pool-15-thread-1] ERROR org.apache.nifi.controller.ExtensionBuilder -- Could not create Processor of type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub from org.apache.nifi:nifi-azure-nar:2.4.0 for ID 9706f422-72e7-4ee9-b7e5-525fab338432 due to: org.apache.nifi.processors.azure.eventhub.PutAzureEventHub; creating "Ghost" implementation
2026-04-02 12:22:09,370 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.370 [pool-14-thread-1] DEBUG org.apache.nifi.manifest.StandardRuntimeManifestService -- Added additionalDetails for org.apache.nifi.processors.standard.HandleHttpResponse from /minifi-data/work/nar/extensions/minifi-standard-nar-2.24.08.0-19.nar-unpacked/META-INF/docs/additional-details/org.apache.nifi.processors.standard.HandleHttpResponse/additionalDetails.md
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut org.apache.nifi.controller.exception.ProcessorInstantiationException: org.apache.nifi.processors.azure.eventhub.PutAzureEventHub
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.ExtensionBuilder.createLoggableProcessor(ExtensionBuilder.java:794)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.ExtensionBuilder.buildProcessor(ExtensionBuilder.java:251)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.flow.StandardFlowManager.createProcessor(StandardFlowManager.java:357)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.flow.AbstractFlowManager.createProcessor(AbstractFlowManager.java:428)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.addProcessor(StandardVersionedComponentSynchronizer.java:2493)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:1052)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:456)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:251)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:668)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3873)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:449)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:221)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1824)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:91)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:778)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:499)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.minifi.c2.command.DefaultUpdateConfigurationStrategy.reloadFlow(DefaultUpdateConfigurationStrategy.java:148)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.minifi.c2.command.DefaultUpdateConfigurationStrategy.update(DefaultUpdateConfigurationStrategy.java:118)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.c2.client.service.operation.UpdateConfigurationOperationHandler.updateFlow(UpdateConfigurationOperationHandler.java:131)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.c2.client.service.operation.UpdateConfigurationOperationHandler.handle(UpdateConfigurationOperationHandler.java:115)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.c2.client.service.C2OperationManager.processOperationsInLoop(C2OperationManager.java:99)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.c2.client.service.C2OperationManager.run(C2OperationManager.java:77)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at java.base/java.lang.Thread.run(Unknown Source)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut Caused by: java.lang.IllegalStateException: Unable to find bundle for coordinate org.apache.nifi:nifi-azure-nar:2.4.0
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.ExtensionBuilder.createLoggableComponent(ExtensionBuilder.java:923)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut at org.apache.nifi.controller.ExtensionBuilder.createLoggableProcessor(ExtensionBuilder.java:780)
2026-04-02 12:22:09,374 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut ... 25 common frames omitted
2026-04-02 12:22:09,378 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.378 [pool-15-thread-1] DEBUG org.apache.nifi.groups.StandardProcessGroup -- Adding GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432] to StandardProcessGroup[identifier=dda165d2-df68-4f0e-903b-2947ee68a3cd,name=root], found no conflicting Version Component ID for ID f141829f-9ecb-4057-934c-124703c27785
2026-04-02 12:22:09,378 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.378 [pool-15-thread-1] DEBUG org.apache.nifi.controller.StandardProcessorNode -- Resetting Validation State of GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432] due to setting process group
2026-04-02 12:22:09,378 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.378 [pool-15-thread-1] INFO org.apache.nifi.groups.StandardProcessGroup -- GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432] added to StandardProcessGroup[identifier=dda165d2-df68-4f0e-903b-2947ee68a3cd,name=root]
2026-04-02 12:22:09,378 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.378 [Validate Components Thread-3] DEBUG org.apache.nifi.controller.AbstractComponentNode -- Updating validation context to StandardValidationContext[componentId=9706f422-72e7-4ee9-b7e5-525fab338432, properties={}]
2026-04-02 12:22:09,379 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.379 [pool-15-thread-1] DEBUG org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer -- Updating Processor GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432]
2026-04-02 12:22:09,379 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.379 [pool-15-thread-1] DEBUG org.apache.nifi.controller.AbstractComponentNode -- Resetting Validation State of GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432] due to setting annotation data
2026-04-02 12:22:09,379 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.379 [pool-15-thread-1] DEBUG org.apache.nifi.controller.AbstractComponentNode -- Reset validation state of GhostProcessor[id=9706f422-72e7-4ee9-b7e5-525fab338432] but will not trigger async validation because trigger has been paused
2026-04-02 12:22:09,379 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.379 [Validate Components Thread-3] DEBUG org.apache.nifi.controller.AbstractComponentNode -- Computed validation errors with Validation Context StandardValidationContext[componentId=9706f422-72e7-4ee9-b7e5-525fab338432, properties={}]; results = ['Missing Processor' validated against 'Any Property' is invalid because Processor is of type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub, but this is not a valid Processor type]
2026-04-02 12:22:36,845 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.845 [Listen to Bootstrap] DEBUG org.apache.nifi.minifi.bootstrap.BootstrapListener -- Listening for Bootstrap Requests
2026-04-02 12:22:36,856 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.856 [NAR Auto-Loader] DEBUG org.apache.nifi.nar.StandardNarLoader -- Unpacking NAR File [nifi-azure-services-api-nar-2.3.0.nar] completed
2026-04-02 12:22:36,899 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.898 [NAR Auto-Loader] WARN org.apache.nifi.nar.NarClassLoaders -- While loading 'com.cloudera:nifi-cdf-debezium-postgresql-nar:1.28.1.2.1.7.2006-1' unable to locate exact NAR dependency 'org.apache.nifi:nifi-standard-services-api-nar:1.28.1.2.1.7.2006-1'. Only found one possible match 'org.apache.nifi:nifi-standard-services-api-nar:2.24.08.0-19'. Continuing...
2026-04-02 12:22:36,899 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.899 [NAR Auto-Loader] DEBUG org.apache.nifi.nar.NarClassLoaders -- Loading NAR file: /minifi-data/work/nar/extensions/nifi-cdf-debezium-postgresql-nar-1.28.1.2.1.7.2006-1.nar-unpacked
2026-04-02 12:22:36,928 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.928 [NAR Auto-Loader] INFO org.apache.nifi.nar.NarClassLoaders -- Loaded NAR file: /minifi-data/work/nar/extensions/nifi-cdf-debezium-postgresql-nar-1.28.1.2.1.7.2006-1.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[/minifi-data/work/nar/extensions/nifi-cdf-debezium-postgresql-nar-1.28.1.2.1.7.2006-1.nar-unpacked]
2026-04-02 12:22:36,928 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.928 [NAR Auto-Loader] WARN org.apache.nifi.nar.NarClassLoaders -- While loading 'org.apache.nifi:nifi-azure-services-api-nar:2.3.0' unable to locate exact NAR dependency 'org.apache.nifi:nifi-standard-shared-nar:2.3.0'. Only found one possible match 'org.apache.nifi:nifi-standard-shared-nar:2.24.08.0-19'. Continuing...
2026-04-02 12:22:36,928 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.928 [NAR Auto-Loader] DEBUG org.apache.nifi.nar.NarClassLoaders -- Loading NAR file: /minifi-data/work/nar/extensions/nifi-azure-services-api-nar-2.3.0.nar-unpacked
2026-04-02 12:22:36,952 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.952 [NAR Auto-Loader] INFO org.apache.nifi.nar.NarClassLoaders -- Loaded NAR file: /minifi-data/work/nar/extensions/nifi-azure-services-api-nar-2.3.0.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[/minifi-data/work/nar/extensions/nifi-azure-services-api-nar-2.3.0.nar-unpacked]
2026-04-02 12:22:36,952 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.952 [NAR Auto-Loader] WARN org.apache.nifi.nar.NarClassLoaders -- While loading 'org.apache.nifi:nifi-azure-nar:2.4.0' unable to locate exact NAR dependency 'org.apache.nifi:nifi-azure-services-api-nar:2.4.0'. Only found one possible match 'org.apache.nifi:nifi-azure-services-api-nar:2.3.0'. Continuing...
2026-04-02 12:22:36,952 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.952 [NAR Auto-Loader] DEBUG org.apache.nifi.nar.NarClassLoaders -- Loading NAR file: /minifi-data/work/nar/extensions/nifi-azure-nar-2.4.0.nar-unpacked
2026-04-02 12:22:36,971 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.971 [NAR Auto-Loader] INFO org.apache.nifi.nar.NarClassLoaders -- Loaded NAR file: /minifi-data/work/nar/extensions/nifi-azure-nar-2.4.0.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[/minifi-data/work/nar/extensions/nifi-azure-nar-2.4.0.nar-unpacked]
2026-04-02 12:22:36,979 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:36.979 [NAR Auto-Loader] INFO org.apache.nifi.nar.StandardNarLoader -- Created class loaders for [3] NAR bundles with [0] skipped Environment Details: MiNiFi version: Java 2.24.08 EFM version: 2.2.0.0-86 All NARs were downloaded from the Cloudera Sonatype Nexus repository. I do not understand where the issue comes from. I would really appreciate your help Best regards,
... View more
Labels:
- Labels:
-
Apache MiNiFi
-
Cloudera Data Flow
07-28-2025
08:15 AM
1 Kudo
I have resolved the issue by installing the nifi-kafka-3-service-nar-2.4.0.nar which added the Kafka3ConnectionService V.2.4.0.
... View more
07-28-2025
02:39 AM
Hello Everyone, We are currently conducting tests and POCs to push (and potentially read) data from Kafka brokers and Azure Event Hubs. Event Hubs Test Our Event Hubs test worked successfully: We added the following NARs as extensions: nifi-azure-nar-2.4.0.nar nifi-azure-services-api-nar-2.3.0.nar After a manifest refresh in EFM, we were able to use the PutAzureEventHub processor. We configured the flow, published the new version, and confirmed that the MiNiFi agent could successfully send data to the Event Hub. Kafka Test Issue We are now trying to create a flow in MiNiFi to push data into a Kafka topic. We followed the same steps as the Event Hubs test and added the following NAR files: nifi-kafka-service-api-nar-2.4.0.nar nifi-kafka-nar-2.4.0.nar What works: After refreshing the manifest, we can see two Kafka processors, including PublishKafka, which we need for the test. What doesn’t work: We cannot add the KafkaConnectionService, which is required to configure the PublishKafka processor. Even after adding the nifi-kafka-service-api-nar-2.4.0.nar and performing a refresh manifest, the KafkaConnectionService controller service does not appear. We also tried Kafka NARs version 2.2.0, with the same result. Environment Details: MiNiFi version: Java 2.24.08 EFM version: 2.2.0.0-86 All NARs were downloaded from the Cloudera Sonatype Nexus repository. Request Could you please advise on: Are we missing a specific Kafka NAR or dependency to get KafkaConnectionService to appear? Is there a version compatibility issue between MiNiFi 2.24.08, EFM 2.2.0.0-86, and the NARs we are using? What steps are recommended to enable Kafka connectivity in this setup? Best regards
... View more
Labels:
- Labels:
-
Apache MiNiFi