# Problem with stopword filter, SimpleQueryStringQuery and default operator AND

**URL:** <https://discuss.elastic.co/t/problem-with-stopword-filter-simplequerystringquery-and-default-operator-and/170930>\
**Category:** Elasticsearch\
**Created:** [March 5, 2019, 2:35pm UTC](https://discuss.elastic.co/t/problem-with-stopword-filter-simplequerystringquery-and-default-operator-and/170930 "2019-03-05T14:35:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xrammit](https://avatars.discourse-cdn.com/v4/letter/x/e99b99/32.png) [@xrammit](https://discuss.elastic.co/u/xrammit)\
**Post date:** [March 5, 2019, 2:35pm UTC](https://discuss.elastic.co/t/problem-with-stopword-filter-simplequerystringquery-and-default-operator-and/170930/1 "2019-03-05T14:35:16Z")

</div>

Hi everybody,

I have a problem with a Simple Query String Query with default operator AND and language-specific stopword filters. I configured the index to apply the stopword filters on the indexed documents (analyzer config parameter) as well as on the search query (search\_analyzer config parameter). However it seems that the stopword filter is not applied correctly on the search query if I query on fields with different search analyzers.

I've built a small example that shows the problem:

1. create an index `mytest` with a custom template

```auto
PUT /mytest

{
  "settings": {
    "analysis": {
      "filter": {
        "english_stop": {
          "type": "stop",
          "stopwords": "_english_"
        },
        "german_stop": {
          "type": "stop",
          "stopwords": "_german_"
        }
      },
      "analyzer": {
        "my_english_analyzer": {
          "tokenizer": "standard",
          "filter": ["english_stop"]
        },
        "my_german_analyzer": {
          "tokenizer": "standard",
          "filter": ["german_stop"]
        }
      }
    }
  },
  "mappings": {
    "_doc": {
      "dynamic": true,
      "dynamic_templates": [
        {
          "english_text": {
            "match": "*_text_en",
            "mapping": {
              "type": "text",
              "analyzer": "my_english_analyzer",
              "search_analyzer": "my_english_analyzer"
            }
          }
        },
        {
          "german_text": {
            "match": "*_text_de",
            "mapping": {
              "type": "text",
              "analyzer": "my_german_analyzer",
              "search_analyzer": "my_german_analyzer"
            }
          }
        }
      ]
    }
  }
}

```

1. add two test documents (one analyzed with `my_english_analyzer` and the other one with `my_german_analyzer`)

```auto
PUT /mytest/_doc/1

{
  "title_text_de": "Frankfurt am Main",
  "content_text_de": "Frankfurt am Main ist die fünftgrößte Stadt Deutschlands."
}

```

```auto
PUT /mytest/_doc/2

{
  "title_text_en": "London",
  "content_text_en": "London is the capital city of the United Kingdom."
}

```

1. Now search for "Frankfurt Main" with default operator AND on all fields (`*_text_*`). The response contains the document with id 1 as expected.

```auto
POST /mytest/_search

{
  "query": {
    "simple_query_string" : {
      "query": "Frankfurt Main",
      "fields": ["*_text_*"],
      "default_operator": "and"
    }
  }
}

```

1. Search again but add the (German) stopword "am" to the query. Now the response contains no document although I expected to find the document with id 1 again as the stopword "am" should be filtered in the search query. The search result is empty as well when using other German stopwords (e.g. "im", "über" etc) or re-ordering the search terms (e.g. "Frankfurt Main am").

```auto
POST /mytest/_search

{
  "query": {
    "simple_query_string" : {
      "query": "Frankfurt am Main",
      "fields": ["*_text_*"],
      "default_operator": "and"
    }
  }
}

```

1. Search again with the stopword but limit the fields to the ones analyzed with `my_german_analyzer` (`*_text_de`). Now the response contains the Frankfurt document as expected. The same holds for searches with other German stopwords or re-ordering the search terms.

```auto
POST /mytest/_search

{
  "query": {
    "simple_query_string" : {
      "query": "Frankfurt am Main",
      "fields": ["*_text_de"],
      "default_operator": "and"
    }
  }
}

```

I did all tests with a clean Elasticsearch 6.6.1 in the official Elasticsearch Docker container.

Is my configuration or expectation wrong or is this a bug in Elasticsearch?  
I did some research on this problem and found the following Github issues that were fixed in Elasticsearch 6.3.x and 6.4.1, respectively. Besides that both seem to be related.

- [Stop-words not removed during simple-query query-time analysis](https://github.com/elastic/elasticsearch/issues/28855)
- [Stop-words not removed in simple\_query\_string when more then one field](https://github.com/elastic/elasticsearch/issues/33009)

---

<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:** [April 2, 2019, 2:35pm UTC](https://discuss.elastic.co/t/problem-with-stopword-filter-simplequerystringquery-and-default-operator-and/170930/2 "2019-04-02T14:35:17Z")

</div>

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