Bengali_normalization not found

Elastic Stack Elasticsearch
1 
PUT doc_bn
{
  "settings": {
    "number_of_shards": 1,
    "number_of_replicas": 0,
    "refresh_interval": "10s",
    "analysis": {
      "filter": {
        "my_stop": {
          "type": "stop",
          "stopwords": "_bengali_"
        },
        "my_stemmer": {
          "type": "stemmer",
          "language": "bengali"
        }
      },
      "analyzer": {
        "my_html": {
          "tokenizer": "standard",
          "char_filter": [
            "html_strip"
          ],
          "filter": [
            "lowercase",
            "indic_normalization",
            "bengali_normalization",
            "my_stop",
            "my_stemmer"
          ]
        }
    }
  },
  "mappings": {
    ...
  }
}

Custom Analyzer [my_html] failed to find filter under name [bengali_normalization]

I supposed it is available from reading the following link:
https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html#bengali-analyzer

GET /
{
  "name": "elasticsearch1",
  "cluster_name": "docker-cluster",
  "cluster_uuid": "6m0JCM_vQv2AnQiNFYx76g",
  "version": {
    "number": "6.0.1",
    "build_hash": "601be4a",
    "build_date": "2017-12-04T09:29:09.525Z",
    "build_snapshot": false,
    "lucene_version": "7.0.1",
    "minimum_wire_compatibility_version": "5.6.0",
    "minimum_index_compatibility_version": "5.0.0"
  },
  "tagline": "You Know, for Search"
}
2

Please format your code using </> icon as explained in this guide. It will make your post more readable.

Or use markdown style like:

```
CODE
```

I suppose you are starting elasticsearch "normally" and that you are not trying to run it embedded from a JVM?

If so, it might be a bug. But could you confirm how you are launching elasticsearch ?

3

I am not sure I understood what you mean with "not trying to run it embedded from a JVM".
But I think I am not, because I am using docker compose using the following images:
docker.elastic.co/elasticsearch/elasticsearch:6.0.1

4

So it looks like a bug. Could you open an issue in GitHub and also link to this discussion ?

5

Done:

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.