Zeebe Importer metadata is saved in Elasticsearch

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Done
    • Priority: L3 - Default
    • 3.6.0-alpha1, 3.6.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      When we process Zeebe data in Elasticsearch, the importers should have their metadata saved in a dedicated index (or the existing import index). This means that Optimize can be restarted and have its importers resume from the point of the last seen records

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: