lordgamez commented on PR #10353:
URL: https://github.com/apache/nifi/pull/10353#issuecomment-3365959944
> Currently the json for a stop flow opearation which is already integrated
in the java solution would be :
>
> ```
> {
> "requested_operations": [
> {
> "identifier": <some-id>,
> "operation": "STOP",
> "operand": "FLOW"
> }
> ]
> }
> ```
>
> I believe this stops everything inside the root process group, and if
anything other than FLOW is sent as operand the command fails
>
> The json for the stop processor command i proposed would look like this:
>
> ```
> {
> "requested_operations": [
> {
> "identifier": <some-id>,
> "operation": "STOP",
> "operand": "PROCESSOR",
> "args": {
> "processorId": "processor_id"
> }
> }
> ]
> }
> ```
>
> This is the implementation i naturally gravitated towards given the
selection machanism of handlers that the java implementation has. It selects
the proper handler based on a combination of operation/operand.
>
> I believe there are already some differences between the interfaces of the
2 implementations.So in order to be compatible with the cpp variant and have
start/stop per processor we would need some sort of detection logic for the
value received in the operand field.
I think this is okay to move forward with this implementation and we'll
adjust minifi-cpp and the open source minifi-c2 server implementation to this
in the future. It will be easier to accept both the old and the new notation in
minifi-cpp for a while until the old notation is taken out in a future release.
--
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]
