Uploaded image for project: 'mod-data-import'
  1. mod-data-import
  2. MODDATAIMP-62

Refactor error handling on JobExecution status update

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 10
    • Story Points:
      5
    • Development Team:
      Folijet

      Description

      Result of an update JobExecution status call should not affect the result of operation performed on another entity, for example on DELETE /data-import/upload/definition/uploadDefinitionId failing updateJobExecutionStatus future should not affect the response in case of successful deletion of the uploadDefinition. Basically, updateJobExecutionStatus future should not be "composed", but instead "handled" and in case of error a comprehensive log should be provided.
      Steps:
      1. Remove compose/add handle(log errors) on updateJobExecution status
      2. If there are files that should be deleted - change flow to deleteFiles --> compose delete upload/file definition
      3. Search for all the cases when the described above flow is applicable and refactor if necessary. Check for similar scenarios in mod-source-record-manager

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Kateryna Senchenko Kateryna Senchenko
                Reporter:
                Kateryna Senchenko Kateryna Senchenko
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases