lordgamez commented on PR #10353:
URL: https://github.com/apache/nifi/pull/10353#issuecomment-3365606622
> I believe it's currently not compatible with the API implemented by MiNiFi
C++, but we're open to an API change if we can agree that the new API is an
improvement, and if we can provide a transition period. I find it difficult to
understand what protocol API this code maps to. In MiNiFi C++, I believe we
have this:
>
> * Operation: START/STOP
> valid "name": C2 | FlowController | <component UUID> | <component
name>
> content / arguments: (empty, not used)
>
>
> From what I understand after talking to @pkedvessy, this pull request adds
a new "name" called "processor, where we would put the processor UUID in the
(currently unused) arguments, as a JSON Object with the key "processorId".
Just to have a clear example currently in MiNiFi C++ the format of the
start/stop request looks like the following where the operand is a processor id:
```
{
"operation": "heartbeat",
"requested_operations": [
{
"operationid": 41,
"operation": "stop",
"operand": "2438e3c8-015a-1000-79ca-83af40ec1991"
}
]
}
```
What is the equivalent json in this case?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
