Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5362 Optimize import gets stuck on nested document limit
  3. OPT-5094

Check for nested limit exception using more specific string terms

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.6.0-alpha1, 3.6.0
    • None
    • backend
    • None
    • Not defined

      In https://github.com/camunda/camunda-optimize/pull/2830#discussion_r514181687, we added a check for the exceptions thrown by Elasticsearch to try to identify where the nested limit had been reached, in order to give users a hint as to how to solve it. However, the string we use to make this check is too broad and results in a lot of false positives (i.e. any nested exception also catches the check and the logged output is irrelevant and misleading). We should be more precise in how we determine whether the exception from elasticsearch actually is relating to the nested limit being reached.

      The following support ticket contains reference to the original problem so could give a clue as to what other parts of the error message could be used: https://jira.camunda.com/browse/SUPPORT-7738

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: