Member since
08-08-2024
114
Posts
28
Kudos Received
14
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 131 | 06-22-2026 10:01 AM | |
| 209 | 06-12-2026 07:16 AM | |
| 494 | 05-26-2026 11:44 AM | |
| 621 | 05-26-2026 09:56 AM | |
| 564 | 04-15-2026 11:56 AM |
05-12-2026
03:06 PM
Hello @nisaar, sftp CLI and PutSFTP can internally work differently. Have you check nifi-app.log from the NiFi nodes to review the error? If so, can you share here the message to take a look.
... View more
05-06-2026
02:07 PM
Hello @Dagonvlg, The best option should be on NiFi UI, in that way you can execute it as stateless: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-stateless-processor-nar/1.28.0/org.apache.nifi.processors.stateless.ExecuteStateless/index.html
... View more
04-24-2026
11:57 AM
1 Kudo
Hello @Dagonvlg, As far as I know, NiFi 2 does not have a stateless mode to the entire service. That was removed. But what it offers is an stateless engine. You can configure it at Processor Group level: https://nifi.apache.org/nifi-docs/user-guide.html#stateless-execution-engine
... View more
04-21-2026
08:43 AM
Hello @dylee, Try with https://archive.cloudera.com/p/cdp-public/ this one do open and have all the available versions.
... View more
04-17-2026
04:16 PM
Hello @MusabAlosaimi, I would suggest to open an administrative case on Lighthouse. They could help you updating your profile.
... View more
04-15-2026
11:56 AM
3 Kudos
Hello @karsten, You should not include anything under the unpacked folder, after a restart it will always remove the content and the new unpack will put only the nar content. Now, you can use the resources path for this, for example: ├── your-nifi-custom-processor
│ ├── pom.xml
│ └── src
│ └── main
│ ├── java
│ ├── resources
│ └── data
│ │ └── config.ini
│ └── webapp This is based on the examples here: https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html You should include all the information on your pom.xml. The resources part should look like this: <resources>
<resource>
<directory>src/main/resources</directory>
<includes>
<include>**/*</include>
</includes>
</resource>
</resources> Also found this interesting blog with the same explanation: https://medium.com/@mr.sinchan.banerjee/nifi-custom-processor-series-part-1-writing-your-first-custom-processor-dd7aa901c896 This is not Cloudera or NiFi official, but it could help you.
... View more
04-09-2026
09:02 AM
1 Kudo
Hello @YSFSK, I understand now. I do see the error you mention: 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 That error points to be a problem with the version. So we are basically on the same point. We have nifi-azure-nar at 2.4.0, nifi-azure-services-api at 2.3.0 and nifi-cdf-debezium-postgresql at 1.28.1. This is a mix that is not working. I do not know the NiFi version you have, but should use that version for all the NARs as well. Using different versions is not a good idea. You can download them from the Sonatype Nexus Repository.
... View more
04-08-2026
01:05 PM
Hello @YSFSK, I do not understand part of your response. I attempted to test the same Debezium NAR with a more recent version, however, we were unable to upload new extensions to EFM. Why you were unable to upload it? Any errors? 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. On the first part you say that tested only with the two Azure NARs on 2.3, which should be good for your version, without the Debezium 1.x, and it worked. Which makes sense that this points to this Debezium 1.x NAR only as it is created for a different version. On Sonatype Nexus Repository I do see Debezium 2.3 version, that is the correct for your environment.
... View more
04-07-2026
02:00 PM
1 Kudo
Hello @YSFSK, MiNiFi version you have is compatible with CFM 4.2.0, which is based on NiFi 2 https://docs.cloudera.com/cem/2.2.0/release-notes-minifi-java/topics/cem-java-agent-processors.html You mentioned you downloaded nifi-cdf-debezium-postgresql-nar-1.28.1.2.1.7.2006-1.nar that is for NiFi 1.28. I checked and the nar is available for different 2.x versions, so you should select one that it matches your NiFi version. Do the same for the other two NARs, they are 2.4 and 2.3, so just make sure they match the actual version.
... View more
03-12-2026
09:53 AM
1 Kudo
Hello @criki, No, PutS3Object itself does not perform MD5 integrity check. This can be confirmed on the processor source code where we do not have any checksum method: https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java On this link you can see how the SDK can configure the MD5 checksum, which is not part of the processor code: https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity-upload.html What you can do is, in your Flow, add a hash and then review it. First with CryptographicHashContent create the hash, then do the PutS3Object. After that, you can confirm it is fine do FetchS3Object then CryptographicHashContent and compare the hash with RouteOnAttribute.
... View more