Robust incremental import of Workflow Data

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 1.0.0, 1.0.0-alpha2
    • Affects Version/s: None
    • Component/s: None
    • None

      AT

      • given
        • As a user I can configure the REST endpoint of a Camunda Engine
      • Once
        • Optimize is started
      • then
        • it starts indexing
        • Indexing fault tolerant
        • Indexing is incremental

      Things to check

      • are updates happening on Historical activity table records?
      • is it possible to perform sorted query?
      • do we need extra hashing on entities in engine?
      • is it possible to request only the data since last indexing from the engine?
      • should partial imports be allowed for statistics, i.e. heatmap, etc.?
      • how to handle load balancing on engine resources, make sure we don't block network\io\cpu with our import requests?
        • do we run against clustered engines?
      • how to handle performance\load balancing on ES nodes\cluster?
        • do we test against multiple nodes of ES?
      • what are common pitfalls that other people face?
      • how do we handle FK's\joins?
        • do we denormalize data?
        • do we import only tables which are used in Optimize right now?
      • should it be possible to configure periodical indexing?

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: