Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3053

Event Based Import #2 Iteration

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: backend
    • Labels:
    • PM Priority:
      100

      Description

      Context:
      Going forward from the beta status reached with OPT-2719 we need to iterate on the overall event based import setup.

      Things to consider are:

      • consider making publish update state, index management & definition import to be controlled on a per process basis rather than having a service doing that cross-process
      • reconsider the usage of a shared vs dedicated import job executor for all active event process instance imports

      AT:

      • rather than having a static import scheduler interval configured we want to use a continuous running import thread (just like the engine import)
      • adopt EventProcessInstanceImportMediator to fully implement the Import architecture(split it up into mediator, indexhandler, make it extend timeStampBasedMediator)
      • rather then reusing the engine import config of the ElasticsearchImportJobExecutor we should have a dedicated configuration for the event import
      • in the indexManager replace the Phaser used to track usages with an atomic int

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            sebastian.bathke Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: