• L

      Context:

      In the context of OPT-3748, where we are thinking of splitting nested documents into their own index, we also decided we would like to dedicate some time to investigate if we can merge duplicated userTask/FlowNode data within our indices

       

      Meeting Notes: https://confluence.camunda.com/display/CO/2020-10-22+Handle+10k+nested+document+limit 

       

      Implementation Notes:

      Unfortunately, due to the nature of this change this ticket can't easily be broken into smaller subtasks, so this ticket will need reviewed as one large PR. I've broken down my implementation into subtasks though for easier handling on my side and for keeping track of progress

      • [x] Figure out relationship between various existing ID fields (eg id, taskId, activityId, activityInstanceId etc)
      • [x] Adjust DTO data structure and field names in BE
      • [x] Make assignee & candidateGroup fields not nested
      • [x] Migration & MigrationIT
      • [x] Adjust userTask and activity import 
      • [x] Adjust report evaluation aggregations & relevant scripts (frequency)
      • [x] Adjust report evaluation aggregations & relevant scripts (duration)
      • [x] Adjust branch analysis aggregations
      • [x] Adjust existing filter aggregations 
      • [x] Adjust preexisting IT
      • [x] Adjust any affected CI jobs

       

       

       

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Helene Waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: