phrocker commented on pull request #4933: URL: https://github.com/apache/nifi/pull/4933#issuecomment-810993766
> > > @ottobackwards I wholeheartedly agree. Here is a quick and dirty summary of the current state of things: > Method of deploying flow nifi-minifi (java) nifi-minifi-cpp > manually author config.yml ✔ ✔ > nifi template xml -> minifi-toolkit -> config.yml ✔ ❌ > change ingestor ✔ [multiple impls](https://github.com/apache/nifi-minifi/tree/main/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors) ❌ > [C2 Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design) ❌ ✔ > > C2 Server Implementations that exist in Apache (i.e., not including any community or vendor solutions): > > * [Server for PullHttpChangeIngestor](https://github.com/apache/nifi-minifi/tree/main/minifi-c2) > > * [WIP PoC server-side implementation](https://github.com/apache/nifi-minifi/tree/minifi-c2-server/minifi-c2) of the [C2 Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design) > > > @arpadboda - did I miss anything? > > Looking towards the future, it is my hope that we can standardize on one approach for both minifi and minifi-cpp. Ideally that is the C2 Protocol with a shared/common server that is compatible with nifi, minifi, and minifi-cpp. I think this PR is the first step towards achieving something like this, as it allows us to much more easily maintain minifi (java) in lockstep with with nifi. From here we have a good foundation to implement a C2 Protocol Client to the same spec supported by minifi-cpp and a corresponding server implementation that can share API code with the java client. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
