jstastny-cz opened a new issue, #2249:
URL: https://github.com/apache/incubator-kie-issues/issues/2249

   As follow-up to #2231 this issue addresses the same for "standalone" jobs 
service.
   
   What has been already adjusted as part of the above:
   * Shared API classes in 
[jobs-service/jobs-service-internal-api](https://github.com/apache/incubator-kie-kogito-apps/tree/main/jobs-service/jobs-service-internal-api)
   * Data Index changes including persistence.
   * Data Audit changes including persistence.
   
   What is the scope of anticipated changes;
   * Persistence changes for jobs-service.
   * Execution exception details capture and promote via events.
   
   The anticipated complexity comes from following differences with the 
Embedded Jobs Addon:
   * Network communication when executing jobs.
     * Need to properly handle network errors and promote into the exception 
details fields.
   * Actual execution taking place in isolated kogito app.
     * The exception needs to be caught in kogito app on the callback URL 
resource and also provided as part of the callback URL response.
     * Jobs Service then needs to consume the response payload and decide.
     * This complicates the "conditional" behavior used for Embedded Jobs 
Addon, which is enabled/disabled via a single property 
`kogito.jobs-service.exception-details-enabled`
       * In this case the property needs to be handled also already in the 
kogito app (kogito-runtimes repo), also together with custom implementations of 
the "Extractor" interface - which would allow users to provide their own impl 
of handling the exception contents (e.g. sanitize security-sensitive contents 
in case of SQL exception or filesystem structure,..)
   * Possibly changes around eventing (which is not used for Embedded Jobs 
Addon).


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to