Re: InvokeGRPC with External Proto
Mike, Bryan - thanks for the info and the offer of help exploring self describing messages - I’ll leave the JIRA ticket for the time being to avoid wasting your time, but if we proceed with development I’ll get back in touch / contribute wherever possible. Thanks, Chris > On 12 Aug 2020, at 20:11, Michael Hogue wrote: > > Chris, > >Currently, the Invoke/Listen grpc processors are bound to a specific proto > IDL defined here: > https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-grpc-bundle/nifi-grpc-processors/src/main/resources/proto/flowfile_service.proto > > <https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-grpc-bundle/nifi-grpc-processors/src/main/resources/proto/flowfile_service.proto> > > When we originally put these together, there wasn't an explicit need for > arbitrary proto IDLs. It may be possible to leverage self-describing messages > documented here: > https://developers.google.com/protocol-buffers/docs/techniques#self-description > > <https://developers.google.com/protocol-buffers/docs/techniques#self-description> > >However, i've not used them personally. If you're interested, create a > Jira ticket and that can be explored. I'm happy to help with the exploration > since I helped put these together originally. > > Thanks, > Mike > > From: Chris Nicholas > Date: Tue, Aug 11, 2020 at 9:21 AM > Subject: InvokeGRPC with External Proto > To: mailto:users@nifi.apache.org>> > > > Hi, > I need to wire an external gRPC service into Nifi - could anyone provide some > pointers on how to change the service IDL / proto within the InvokeGRPC > processor to support the existing external gRPC service proto definitions? > Am trying to avoid having to writing a middleware processor to invoke the > external service ideally. > Thanks > Chris
RE: InvokeGRPC with External Proto
Chris, Currently, the Invoke/Listen grpc processors are bound to a specific proto IDL defined here: https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-grpc-bundle/nifi-grpc-processors/src/main/resources/proto/flowfile_service.proto When we originally put these together, there wasn't an explicit need for arbitrary proto IDLs. It may be possible to leverage self-describing messages documented here: https://developers.google.com/protocol-buffers/docs/techniques#self-description However, i've not used them personally. If you're interested, create a Jira ticket and that can be explored. I'm happy to help with the exploration since I helped put these together originally. Thanks, Mike From: Chris Nicholas > Date: Tue, Aug 11, 2020 at 9:21 AM > Subject: InvokeGRPC with External Proto > To: > > > Hi, > I need to wire an external gRPC service into Nifi - could anyone provide > some pointers on how to change the service IDL / proto within the > InvokeGRPC processor to support the existing external gRPC service proto > definitions? > Am trying to avoid having to writing a middleware processor to invoke the > external service ideally. > Thanks > Chris
Re: InvokeGRPC with External Proto
Hi Chris, I don't know much about gRPC, but the proto file is here: https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-grpc-bundle/nifi-grpc-processors/src/main/resources/proto I think you'd have to build a custom version of this NAR where you changed the proto file and probably also the processor. -Bryan On Tue, Aug 11, 2020 at 9:21 AM Chris Nicholas wrote: > > Hi, > > I need to wire an external gRPC service into Nifi - could anyone provide > some pointers on how to change the service IDL / proto within the > InvokeGRPC processor to support the existing external gRPC service proto > definitions? > > Am trying to avoid having to writing a middleware processor to invoke the > external service ideally. > > Thanks > > Chris >
InvokeGRPC with External Proto
Hi, I need to wire an external gRPC service into Nifi - could anyone provide some pointers on how to change the service IDL / proto within the InvokeGRPC processor to support the existing external gRPC service proto definitions? Am trying to avoid having to writing a middleware processor to invoke the external service ideally. Thanks Chris
