Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-3242

Fix match analysis on API usage

    XMLWordPrintable

Details

    • Critical
    • Hide
      - Task is now locked immediately after match analysis is scheduled.
      - PauseMatchAnalysis worker now returns an error in case after maximum wait time language resource is still not available.
      - Documentation updated
      Show
      - Task is now locked immediately after match analysis is scheduled. - PauseMatchAnalysis worker now returns an error in case after maximum wait time language resource is still not available. - Documentation updated
    • -

    Description

      Problem

      After the translate5 - 5.8.5 update and the introduction of pausing of match analysis in case the memory is not available, some additional improvements and fixes are required for translate5 api usage.

      • currently if the analysis pause worker exceeds the waiting time and there are still unavailable memories, no exception is thrown and the analysis will continue.
      • when pretranslation or analysis operation is triggered the task should be locked with analysis state immediately and not in the analysis worker. With this, on api usage, the user will get the analysis task status with the initial request.
      • confluence documentation is missing for analysis pause

      Developer note: check/test the translate5 frontend after those changes. Especially after the status change!

      Attachments

        Activity

          People

            leonkiz Leon Kiz
            aleksandar Aleksandar Mitrev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: