Use ElasticSearchSchemaManager from upgrade module

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.4.0-alpha1, 2.4.0
    • Affects Version/s: None
    • Component/s: 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

              Assignee:
              Unassigned
              Reporter:
              Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: