wmedvede commented on issue #2231:
URL: 
https://github.com/apache/incubator-kie-issues/issues/2231#issuecomment-3877495448

   Hi Jan, thanks for opening this issue.
   
   So, if my understanding is correct, the idea is to give users more 
information about a potential Job failure, for example via the Data Index API. 
right?  And, following the example with the fields `exceptionMessage` and 
`exceptionDetails`, you mentioned above, uses will be able to execute a DI 
graphql query like this:
   
   **Example of query with extended fields:**
   
   ```
   {
       Jobs {
         id,
         processId,
         processInstanceId,
         status,
         retries,
   
         //extended fields
         exceptionMessage,
         exceptionDetails,
   
       }
   }
   
   ```
   
   **Example of query result with the extended fields for a failing Job:**
   
   ```
   {
     "data": {
       "Jobs": [
         {
           "id": "TIMER_0",
           "processId": "HelloWorld",
           "processInstanceId": "2ab0fabf-fd51-4201-96bf-393e5ab3b098",
           "status": "ERROR",
           "retries": 62,
           
           "exceptionMessage": "Relevant exception message picked up during the 
job execution"
           "exceptionDetails": "Relevant details",
         }
       ]
     }
   }
   ```
   
   My only concerns are:
   
   1) If the change is only implemented for the `kogito-addons-quarkus-jobs`  
add-on, users of the `kogito-addons-quarkus-jobs-service-embedded` and  
`jobs-service-postgresql` variants will see this a Bug. No information error 
informaiton will be populated in these cases.
   
   2) When you comment that the "Standalone" Jobs Service implementation (would 
require changes also in kogito runtimes service area).  Which changes are 
requied in the runtimes? 
   The Job is in the end executed in the Job service side, so the potential 
error should be availabe there I think.
   
   
   
   
   
   


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