# How to use other language stop filter in \_analyze?

**URL:** <https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767>\
**Category:** Elasticsearch\
**Created:** [November 24, 2022, 3:02pm UTC](https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767 "2022-11-24T15:02:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Gattinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_gattinger/32/99690_2.png) [@Michael\_Gattinger](https://discuss.elastic.co/u/Michael_Gattinger)\
**Post date:** [November 24, 2022, 3:02pm UTC](https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767/1 "2022-11-24T15:02:00Z")

</div>

Hi,

> **[Standard analyzer | Elasticsearch Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-standard-analyzer.html)**

States that it has a  
[Stop Token Filter] (disabled by default)  
So to test the Standard Analyzer we type:

```auto
POST _analyze
{
  "analyzer": "standard",
  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
}

```

Now I want to add a german stopword filter.

> **[Stop token filter | Elasticsearch Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html)**

States:

```auto
GET /_analyze
{
  "tokenizer": "standard",
  "filter": ["stop"],
  "text": "a quick fox jumps over the lazy dog"
}

```

Sadly the site does not explain how to activate a stopfilter for another language.

How do you do so?

Here is what I have tried:

```auto
POST /_analyze
{
  "tokenizer": "standard",
  "filter": ["german_stop"],
  "text": "Elasticsearch ist leider sehr schlecht dokumentiert, weshalb ich die Lösung nicht finde."
}

```

Thanks - Enomine

---

<div class="post-metadata">

**Author:** ![Michael\_Gattinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_gattinger/32/99690_2.png) [@Michael\_Gattinger](https://discuss.elastic.co/u/Michael_Gattinger)\
**Post date:** [November 24, 2022, 3:03pm UTC](https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767/2 "2022-11-24T15:03:29Z")

</div>

And why is the first line sometimes

```auto
"tokenizer": "standard",

```

and in other cases

```auto
"analyzer": "standard",

```

?

Is that no difference?

Thanks - Enomine

---

<div class="post-metadata">

**Author:** ![vincenbr](https://avatars.discourse-cdn.com/v4/letter/v/8edcca/32.png) [@vincenbr](https://discuss.elastic.co/u/vincenbr)\
**Post date:** [November 24, 2022, 5:47pm UTC](https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767/3 "2022-11-24T17:47:37Z")

</div>

Hi Michael,  
Regarding your second question, you should read [Anatomy of an analyzer | Elasticsearch Guide [8.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/analyzer-anatomy.html) before.  
Regarding testing the `stop` token filter, it is stated clearly in the configurable parameters, in [Stop token filter | Elasticsearch Guide [8.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html#analysis-stop-tokenfilter-configure-parms)  
So you can use something like

```auto
POST /_analyze
{
  "tokenizer": "standard",
  "filter": [ {
          "type": "stop",
          "ignore_case": true,
          "stopwords" : "_german_"
        } ],
  "text": "Elasticsearch ist ziemlich gut dokumentiert, aber die Konzepte sind manchmal etwas kompliziert. Zum Glück gibt es die Community"
}

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 22, 2022, 5:48pm UTC](https://discuss.elastic.co/t/how-to-use-other-language-stop-filter-in-analyze/319767/4 "2022-12-22T17:48:13Z")

</div>

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