We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1883

Use ElasticSearchSchemaManager from upgrade module

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.4.0-alpha1, 2.4.0
    • None
    • backend
    • None

      Given:
      I execute the upgrade module from optimize 2.X.0 to 2.Y.0

      When:
      There is a new index in 2.Y.0 but there is no explicit upgrade step to create this index

      Then:
      This index is not present after executing the upgrade

      Expected:
      After executing the upgrade the schema should be fully initialized to the state of the target version without the need for explicit IndexCreate upgrade steps

      Notes:
      The upgrade module currently doesn't handle new indexes created in a given version unless an explicit migration step is added.
      In order to handle this scenario automatically we should utilize the ElasticSearchSchemaManager as a last step during the upgrade.

        This is the controller panel for Smart Panels app

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

            Use ElasticSearchSchemaManager from upgrade module

              • Icon: Task Task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 2.4.0-alpha1, 2.4.0
              • None
              • backend
              • None

                Given:
                I execute the upgrade module from optimize 2.X.0 to 2.Y.0

                When:
                There is a new index in 2.Y.0 but there is no explicit upgrade step to create this index

                Then:
                This index is not present after executing the upgrade

                Expected:
                After executing the upgrade the schema should be fully initialized to the state of the target version without the need for explicit IndexCreate upgrade steps

                Notes:
                The upgrade module currently doesn't handle new indexes created in a given version unless an explicit migration step is added.
                In order to handle this scenario automatically we should utilize the ElasticSearchSchemaManager as a last step during the upgrade.

                  This is the controller panel for Smart Panels app

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

                          Created:
                          Updated:
                          Resolved:

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

                                Created:
                                Updated:
                                Resolved: