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

Save multiple target for the same source to t5memory

XMLWordPrintable

    • High
    • Hide
      Due to a t5memory bug since some time segments, that share the same source but differ only in target and timestamp are saved as duplicates.
      Usually the newer segment should overwrite the older one in such a situation. And duplicates should only be stored, if author or other attributes differ.
      With soon coming t5memory 0.7 this will be solved and per default such duplicates will be overwritten again - what will lead to loss of all those duplicates in case of content conversion or TM reorganize, for example.
      As preparation for t5memory 0.7 we introduce the new system config saveDifferentTargetsForSameSource. By default it is disabled. If you activate it, even with t5memory 0.7 those duplicates will still be saved/kept.
      Show
      Due to a t5memory bug since some time segments, that share the same source but differ only in target and timestamp are saved as duplicates. Usually the newer segment should overwrite the older one in such a situation. And duplicates should only be stored, if author or other attributes differ. With soon coming t5memory 0.7 this will be solved and per default such duplicates will be overwritten again - what will lead to loss of all those duplicates in case of content conversion or TM reorganize, for example. As preparation for t5memory 0.7 we introduce the new system config saveDifferentTargetsForSameSource. By default it is disabled. If you activate it, even with t5memory 0.7 those duplicates will still be saved/kept.
    • Added config which purpose is to force t5memory to store segments with the same source as duplicates

      Problem

      Due to a bug in t5memory for some time we save duplicats, where source is the same and target differs - even if all attributes except date are the same.

      This is usually unwanted behavior - older match should be overwritten.

      With 0.7.x version this is fixed and duplicates will only be created, if some attributes except date differ.

      Yet some clients may want to save such duplicates anyway.

      Therefore in t5memory 0.7.x it can be configured in the config and as param for update/reorganize/mass-deletion/tmx-import, if such duplicates should be saved or overwrite older match.

      This param is called saveDifferentTargetsForSameSource.

      Solution

      We should pass saveDifferentTargetsForSameSource with everyx  make it configurable on instance level in translate5, how t5memory behaves with update/reorganize/mass-deletion/tmx-import requests.

      Default should be saveDifferentTargetsForSameSource=0 - so do not save different targets.

      This must be implemented and released, before 0.7.x is going to production to allow users to change it (t5memory 0.6.x does not mind, if a param is send to it, that will only exist in later version). 

            leonkiz Leon Kiz
            marcmittag Marc Mittag [Administrator]
            Sanya Mikhliaiev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: