Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2495 Support ElasticSearch 7.x
  3. OPT-3115

Adopt to Elasticsearch 7.X count api totalHits change

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha1, 3.0.0
    • None
    • None
    • None

      Context:
      With Elasticsearch 7.x. the totalHits response of the search response changed.
      This caused some of our nightly import tests to fail where we expect exact counts to be returned while the counts are by default not guaranteed to be exact anymore.

      AT:

      • any document count asserts utilize the dedicated count api instead of reading the total hits from a search response where possible
      • alternatively the param `.trackTotalHits(true)` is set on any search request where we need exact counts

        This is the controller panel for Smart Panels app

            [OPT-3115] Adopt to Elasticsearch 7.X count api totalHits change

            There are no comments yet on this issue.

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

                Created:
                Updated:
                Resolved: