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

Ngram big difference warning after upgrade

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 2.4.0-alpha2, 2.4.0
    • None
    • backend
    • None

    Description

      Given:
      I upgraded from version 2.3.0 to 2.4.0

      When:
      I start optimize

      Then:
      I see ngram max difference warning in the log

      Expected:
      I don't see ngram related warnings, as they have been resolved by a index settings config change with OPT-1817

      Notes:
      Due to that during migration the index settings don't get updated but during every restart the mappings get updated we see the ngram difference warning after migrating from <=2.3.0 to 2.4.0.

      11:58:35.895 [I/O dispatcher 1] WARN  org.elasticsearch.client.RestClient - request [PUT http://localhost:9200/optimize-import-index/_mapping/import-index?master_timeout=30s&timeout=30s] returned 1 warnings: [299 Elasticsearch-6.2.0-37cdac1 "Deprecated big difference between max_gram and min_gram in NGram Tokenizer,expected difference must be less than or equal to: [1]" "Wed, 30 Jan 2019 10:58:35 GMT"]
      

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce