question Re: Migrating from NiFi 1.21 to 2.6.0 – InvokeGRPC Processor Removed, What Are the Risks of Using Old NAR? in Support Questions

Migrating from NiFi 1.21 to 2.6.0 – InvokeGRPC Processor Removed, What Are the Risks of Using Old NAR?

KMrunal — Wed, 26 Nov 2025 13:24:08 GMT

I’m currently migrating from Apache NiFi 1.21 to NiFi 2.6.0. In my existing flow, I was using the InvokeGRPC processor, but I noticed that this processor has been removed in NiFi 2.x versions.

I have a few questions:

What is the exact reason for deprecating and removing InvokeGRPC in NiFi 2.x?
Was it due to architectural changes, performance issues, or security concerns?
If we take a fork of the NiFi 1.21 gRPC NAR and use it in NiFi 2.6.0, will that work?
- Are there any known performance risks with this approach?
- Could this introduce security vulnerabilities in the current or future releases?
Is there an alternative recommended approach for gRPC integration in NiFi 2.x?
For example, should we use ExecuteScript, custom processors, or any official replacement?

Any insights or official guidance would be greatly appreciated. Thanks in advance!

Re: Migrating from NiFi 1.21 to 2.6.0 – InvokeGRPC Processor Removed, What Are the Risks of Using Old NAR?

VidyaSargur — Thu, 27 Nov 2025 10:09:55 GMT

@KMrunal, Welcome to our community! To help you get the best possible answer, I have tagged in our NiFi experts @MattWho and @haridjh, who may be able to assist you further.

Please feel free to provide any additional information or details about your query. We hope that you will find a satisfactory solution to your question.

Re: Migrating from NiFi 1.21 to 2.6.0 – InvokeGRPC Processor Removed, What Are the Risks of Using Old NAR?

vafs — Thu, 27 Nov 2025 18:02:30 GMT

Hello @KMrunal,

Thanks for being part of Cloudera Community.

I will try to answer your questions:

1. What is the exact reason for deprecating and removing InvokeGRPC in NiFi 2.x?
Answer: This was done because those processors were not really well maintened, so there was some tech debt that was not easy to solve.
That is explained on https://issues.apache.org/jira/browse/NIFI-12069 and https://issues.apache.org/jira/browse/NIFI-12071

2. If we take a fork of the NiFi 1.21 gRPC NAR and use it in NiFi 2.6.0, will that work?
Answer: That may work if you take the fork and rebuild it for NiFi 2.6.0. Now, this can cause problems due to dependencies, such as Netty, that is also documented here: https://issues.apache.org/jira/browse/NIFI-12367
And of course, there can be CVEs that are not solved because the processor was not properly maintained on those versions.

3. Is there an alternative recommended approach for gRPC integration in NiFi 2.x?
Answer: per the context, I understand you're using standalone NiFi implementation, not CFM from Cloudera.
ExecuteScript can be used.
There is no specific alternatives offered, and tell to use custom processors:
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-grpc-nar/1.5.0/org.apache.nifi.processors.grpc.InvokeGRPC/index.html
Checking the CDF from Cloudera, we do offer InvokeGRPC in our CFM 4.11.0:
https://docs.cloudera.com/cfm/4.11.0/release-notes/topics/cfm-supported-processors.html
That version includes NiFi 2.4.0.
So that could be an option if you use CDF.

Re: Migrating from NiFi 1.21 to 2.6.0 – InvokeGRPC Processor Removed, What Are the Risks of Using Old NAR?

KMrunal — Fri, 28 Nov 2025 10:00:47 GMT

@vafsThank you for the detailed information, this fully clarifies the deprecation rationale, possible workarounds, and alternative approaches for gRPC integration in NiFi 2.x!