Custom analyzers in Elasticsearch no longer work

[MikeAlhayek]

Describe the bug

When specifying a custom analyzer in Elasticsearch as explained here https://docs.orchardcore.net/en/latest/reference/modules/Elasticsearch/#elasticsearch-analyzers it does create that custom analyzer in the Elasticsearch service.

Orchard Core version

2.x

To Reproduce

Configure custom analyzer like this:

"OrchardCore_Elasticsearch": {
      // Other settings
      "Analyzers": {
        "standard": {
          "type": "standard"
        },
        "keyword": {
          "type": "keyword"
        },
        "whitespace": {
          "type": "whitespace"
        },
        "knowledgebase_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "lowercase",
            "stop"
          ],
          "char_filter": [
            "html_strip"
          ]
        }
      }
    }

Create an index using the custom knowledgebase_analyzer. Now try to search for anything you'll get an error

[multi_match] analyzer [knowledgebase_analyzer] not found

This issue was caused by PR #16843

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[denispetrische]

I applied this configuration

"OrchardCore_Elasticsearch": {
  "ConnectionType": "SingleNodeConnectionPool",
  "Url": "http://localhost",
  "Ports": [ 9200 ],
  "Analyzers": {
    "standard": {
      "type": "standard"
    },
    "keyword": {
      "type": "keyword"
    },
    "whitespace": {
      "type": "whitespace"
    },
    "knowledgebase_analyzer": {
      "type": "custom",
      "tokenizer": "standard",
      "filter": [
        "lowercase",
        "stop"
      ],
      "char_filter": [
        "html_strip"
      ]
    }
  }
}

Created index with knowledgebase_analyzer

We can see that analyzer were created under name "default", it is necessary because for now there is no mechanism to specify concrete field for analyzer to be applied.

You can see also, that char filters are still not supported.

I created few Menu content Items, I can see them in the default_my index directly

I created a query and it works

I created also multimatch query

So... everything works fine