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-3001

Configure Indices managed by the SchemaManager in a central place

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.2.0-alpha1, 3.2.0
    • None
    • backend
    • None
    • 99
    • Not defined

      Context:

      The ElasticSearchSchemaManager currently creates/updates most of our indices. The indices that are managed by the manager is determined by whether or not the Index class has a @Component annotation. This is not always obvious and doesn't include every index. Current exceptions are the EventProcessInstanceIndex and will also include the indices created for completed camunda activities by definition key. To make this more transparent, we should declare in a more obvious way which indices we want the manager to manage for us. It will also be simpler to make accurate test assertions if we have a list of managed indices, rather than just asserting on expected index counts (see SchemaInitializerIT.java for example).

      AT:

      • Instead of the annotation, declare managed indices for the schema manager to use when creating/updating indices (mappings property)
      • Update all tests that assert on the number of indices that should exist to now include assertions on exactly what indices to expect

        This is the controller panel for Smart Panels app

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

            Configure Indices managed by the SchemaManager in a central place

              • Icon: Task Task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 3.2.0-alpha1, 3.2.0
              • None
              • backend
              • None
              • 99
              • Not defined

                Context:

                The ElasticSearchSchemaManager currently creates/updates most of our indices. The indices that are managed by the manager is determined by whether or not the Index class has a @Component annotation. This is not always obvious and doesn't include every index. Current exceptions are the EventProcessInstanceIndex and will also include the indices created for completed camunda activities by definition key. To make this more transparent, we should declare in a more obvious way which indices we want the manager to manage for us. It will also be simpler to make accurate test assertions if we have a list of managed indices, rather than just asserting on expected index counts (see SchemaInitializerIT.java for example).

                AT:

                • Instead of the annotation, declare managed indices for the schema manager to use when creating/updating indices (mappings property)
                • Update all tests that assert on the number of indices that should exist to now include assertions on exactly what indices to expect

                  This is the controller panel for Smart Panels app

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

                          Created:
                          Updated:
                          Resolved:

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

                                Created:
                                Updated:
                                Resolved: