Refactor EventProcessService class to reduce number of ES request for removing associated resources on delete

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: backend
    • Not defined

      In the EventProcessService class we have a method called bulkDeleteEventProcessMappings and which is responsible for the bulk deletion of event process mappings. For the correct deletion of the mappings, it is necessary to remove first all the associated resources to them, such as

      • reports
      • scope entries from collections
      • event process publish state

      Currently the way we do this is to issue an update_by or delete_by request to ES for each individual eventProcessMappingId. The goal of that ticket is to conduct these operations for all eventProcessMappingIds in fewer ES requests.

            Assignee:
            Unassigned
            Reporter:
            Andromachi Rozaki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: