Remove small field optimization of damages computation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Execution Team 2022-09-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a small field optimization whenever we compute damages that will treat the field + value as part of a damage. This is meant to reduce the total number of damages as it would help merge nearby damages if they are only separated by a small field.

      However, this can cause potential runoffs if all the fields are considered small, leading to all of them being considered as part of a damage. In some instances this can cause a single damage to contain 90%+ of the original document even if it only modified a few bytes initially.

      To avoid this the optimization should be removed.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: