# Replacing filtered and or filter query with bool (Elasticsearch 5.2)

**URL:** <https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596>\
**Category:** Elasticsearch\
**Created:** [March 14, 2017, 8:31pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596 "2017-03-14T20:31:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukejolly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukejolly/32/9951_2.png) [@lukejolly](https://discuss.elastic.co/u/lukejolly)\
**Post date:** [March 14, 2017, 8:31pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596/1 "2017-03-14T20:31:22Z")

</div>

I upgraded to Elasticsearch 5.2 and this query no longer works:

```
POST _search
{
  "size":3000,
  "query":{
    "filtered":{
      "query":{
        "range":{
          "@timestamp":{"gt":"now-2m", "lte":"now"}
        }
      },
      "filter":{
         "or":[
          {"term":{"severity":"ERROR"}},
          {"term":{"severity":"FATAL"}}
        ]
      }
    }
  }
}

```

It resulted in this error:

```
{"error":{"root_cause":[{"type":"parsing_exception","reason":"no [query] registered for [filtered]","line":1,"col":42}],"type":"parsing_exception","reason":"no [query] registered for [filtered]","line":1,"col":42},"status":400}

```

After switching to using bool and must and leaving the filter or I got this error:

```
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[or] query malformed, no start_object after query name","line":1,"col":168}],"type":"parsing_exception","reason":"[or] query malformed, no start_object after query name","line":1,"col":168},"status":400}

```

I thought this would work, but it's returning no results when it should:

```
POST _search
{
  "size":3000,
  "query":{
    "bool":{
      "must":{
        "range":{
          "@timestamp":{"gt":"now-2m", "lte":"now"}
        }
      },
      "should":[
          {"term":{"severity":"ERROR"}},
          {"term":{"severity":"FATAL"}}
      ],
      "minimum_should_match": 1
    }
  }
}

```

What am I missing?

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [March 14, 2017, 10:56pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596/2 "2017-03-14T22:56:08Z")

</div>

Hi,

the query looks okay, the problem might have to do with changes on the default mapping for string fields. When I tried reproducing this I directly indexed documents like this without defining a mapping:

```auto
PUT /test/type/1
{
  "@timestamp" : "2017-03-14",
  "severity" : "FATAL"
}

```

The mapping this creates in 5.2 looks like this:

```auto
{
  "test": {
    "mappings": {
      "type": {
        "properties": {
          "@timestamp": {
            "type": "date"
          },
          "severity": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          }
        }
      }
    }
  }
}

```

This means that the `severity` field itself is analyzed (thus lowercased) and doesn't match the upper case "ERROR" in your term query. If you use the `severity.keyword` field instead it should work:

```auto
OST /test/type/_search
{
  "size":3000,
  "query":{
    "bool":{
      "must":{
        "range":{
          "@timestamp":{"gt":"now-2m", "lte":"now"}
        }
      },
      "should":[
          {"term":{"severity.keyword":"ERROR"}},
          {"term":{"severity.keyword":"FATAL"}}
      ],
      "minimum_should_match": 1
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [March 15, 2017, 12:28pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596/3 "2017-03-15T12:28:42Z")

</div>

I forgot to mention: since you had the `or` part in a filter in the original query and you are not interested in scoring for this part, you should put it in the `filter` section of the overall `bool` query now. Combining the two clauses should work smothing like this:

```auto
...
"bool": {
      "must": { ... },
      "filter": {
        "bool": {
          "should": [
            {
              "term": {
                "severity.keyword": "ERROR"
              }
            },
            {
              "term": {
                "severity.keyword": "FATAL"
              }
            }
          ],
          "minimum_should_match": 1
        }
      }
    }
...

```

---

<div class="post-metadata">

**Author:** ![lukejolly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukejolly/32/9951_2.png) [@lukejolly](https://discuss.elastic.co/u/lukejolly)\
**Post date:** [March 15, 2017, 7:33pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596/4 "2017-03-15T19:33:19Z")

</div>

Thanks tons! This fixed that query and got me on the right track for fixing the rest of mine.

---

<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 12, 2017, 7:33pm UTC](https://discuss.elastic.co/t/replacing-filtered-and-or-filter-query-with-bool-elasticsearch-5-2/78596/5 "2017-04-12T19:33:38Z")

</div>

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