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

Remove HeatmapTargetValueIndex from Elasticsearch

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha1
    • Component/s: backend
    • Labels:
      None

      Description

      Context:
      Till Optimize 2.2 there was an HeatmapTargetValueIndex added which wasn't used in Optimize anymore so we removed it from index creation. However, if a customer migrated from older versions this index still exists in Elasticsearch.

      Proposed Solution:
      We should add a migration step where remove the HeatmapTargetValueIndex.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              johannes.heinemann Johannes Heinemann
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: