# Enable\_position\_increment in query\_string

**URL:** <https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413>\
**Category:** Elasticsearch\
**Created:** [January 31, 2017, 7:17pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413 "2017-01-31T19:17:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shai\_Erera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shai_erera/32/13492_2.png) [@Shai\_Erera](https://discuss.elastic.co/u/Shai_Erera)\
**Post date:** [January 31, 2017, 7:17pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/1 "2017-01-31T19:17:17Z")

</div>

Hi, per the documentation here [https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html), the property `enable_position_increments` is supposed to be defined in the query body, however when I send a request (on `master`) to an index I get:

```
{
  "error": {
    "root_cause": [
      {
        "type": "parsing_exception",
        "reason": "[query_string] query does not support [enable_position_increments]",
        "line": 14,
        "col": 34
      }
    ],
    "type": "parsing_exception",
    "reason": "[query_string] query does not support [enable_position_increments]",
    "line": 14,
    "col": 34
  },
  "status": 400
}

```

`QueryStringQueryBuilder` defines the property as: `private static final ParseField ENABLE_POSITION_INCREMENTS_FIELD = new ParseField("enable_position_increment");` (note, without the terminal 's')

So, is this a documentation issue, or a code issue? If I send the query without the terminal 's', it works, so seems like a documentation issue?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [January 31, 2017, 8:01pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/2 "2017-01-31T20:01:03Z")

</div>

> [@Shai\_Erera](#):
>
> So, is this a documentation issue, or a code issue? If I send the query without the terminal 's', it works, so seems like a documentation issue?

I'll look into it. One moment.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [January 31, 2017, 8:10pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/3 "2017-01-31T20:10:41Z")

</div>

It looks like it was a typo was introduced in 5.0. I'll open a PR with a fix. For now use the name that works. I'll keep support for that name in the 5.x line of Elasticsearch and remove it in 6.0.

---

<div class="post-metadata">

**Author:** ![Shai\_Erera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shai_erera/32/13492_2.png) [@Shai\_Erera](https://discuss.elastic.co/u/Shai_Erera)\
**Post date:** [January 31, 2017, 8:36pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/4 "2017-01-31T20:36:00Z")

</div>

Thanks @nik9000, I'll use `enable_position_increment` then.

> I'll keep support for that name in the 5.x line of Elasticsearch and remove it in 6.0

What do you mean? It (`enable_position_increments`) doesn't seem to be supported at all, no?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [January 31, 2017, 8:37pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/5 "2017-01-31T20:37:55Z")

</div>

I'll add support for `enable_position_increments` and deprecate `enable_position_increment`. It'd be less work if I could just update the documentation but in this case the thing you are enabling is really called "position increments" not "position increment".

---

<div class="post-metadata">

**Author:** ![Shai\_Erera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shai_erera/32/13492_2.png) [@Shai\_Erera](https://discuss.elastic.co/u/Shai_Erera)\
**Post date:** [January 31, 2017, 8:56pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/6 "2017-01-31T20:56:48Z")

</div>

Gotcha. Thanks!

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [January 31, 2017, 9:21pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/7 "2017-01-31T21:21:11Z")

</div>

> <https://github.com/elastic/elasticsearch/pull/22895>

---

<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:** [February 28, 2017, 9:21pm UTC](https://discuss.elastic.co/t/enable-position-increment-in-query-string/73413/8 "2017-02-28T21:21:23Z")

</div>

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