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

(Data Warehouse) Make sure reimport from engine is not necessary

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • None

       

      In certain situations it becomes necessary to reimport data from the process engine. 

      This is e.g. the case when we add new features (e.g. incident information) or new aggregations that require new data from the engine. 

      In certain scenarios the engine does not have the data anymore (e.g. because of history cleanup).

      From Optimize perspective I still would like to use all the new functionality - even for old data - so that I do not have to reimport from the engine where the data does not exist anymore.

      Potential solutions include:

      • copy of engine history (Relational)
      • raw history from engine in elastic without aggregations (complete dump)

       

        This is the controller panel for Smart Panels app

            [OPT-3688] (Data Warehouse) Make sure reimport from engine is not necessary

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10921. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10921 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              felix.mueller Felix Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: