Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
Current Situation
We assume we have a job chain with a <file_order_sink .../> configuration.
- The web services ./job_chain/p and ./job_chains/p response an end node with file order sink attributes ("move" and "remove").
file order sink example
{ "name": "example", "remove": false, "move": "/path/to/archive" }
- The JobScheduler creates a job /scheduler_file_order_sink which is the job of a "normal" job chain node and in addition it creates a new temporary end node.
So, the web services don't reflect the JobScheduler. In particular the node doesn't have functions in JOC Cockpit such as "unstop job" etc. If the /scheduler_file_order_sink job is stopped then you did't have any options to change this situation.
Desired Behavior
- The web services ./job_chain/p and ./job_chains/p response a "normal" job chain node with an additional end node
normal job chain node for permanent information
{ "name": "example", "nextNode": "fileOrderSinkEnd", "errorNode": "fileOrderSinkEnd", "job": { "path": "/scheduler_file_order_sink" }, "level": 0 }
- The web services ./job_chain and ./job_chains response a "normal" job chain node with "move" and "remove" attributes and an additional end node
normal job chain node for volatile information with move and remove attribute in case of a file order sink
{ "name": "example", "state": { "severity": 4, "_text": "ACTIVE" } "job": { "path": "/scheduler_file_order_sink", "state": { "severity": 1, "_text": "PENDING" } }, "level": 0, "remove": false, "move": "/path/to/archive" }
- JOC Cockpit Gui has to consider that a "normal" job chain node can have the new attributes "move" or "remove". In this case the attributes should be displayed instead of the job name "/scheduler_file_order_sink".
- The web services ./jobs and ./jobs/p retain unchanged. The job /scheduler_file_order_sink will not displayed in JOC Cockpit.