# Track total hits: support by integer?

**URL:** <https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232>\
**Category:** Elasticsearch\
**Created:** [January 22, 2019, 12:54pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232 "2019-01-22T12:54:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kzzzzo2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kzzzzo2/32/40077_2.png) [@kzzzzo2](https://discuss.elastic.co/u/kzzzzo2)\
**Post date:** [January 22, 2019, 12:54pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232/1 "2019-01-22T12:54:53Z")

</div>

An exception occurred when setting an integer to `track_total_hits`.

The doc is written as `set track_total_hits as an integer`.

Is there a way to set an integer?

### Version

7.0.0-alpha2

### Request

```json
GET _search
{
  "track_total_hits": 100,
  "query": {
    "match_all": {}
  }
}

```

### Response

```json
{
  "error": {
    "root_cause": [
      {
        "type": "json_parse_exception",
        "reason": "Current token (VALUE_NUMBER_INT) not of boolean type\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@6e6e840f; line: 2, column: 26]"
      }
    ],
    "type": "json_parse_exception",
    "reason": "Current token (VALUE_NUMBER_INT) not of boolean type\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@6e6e840f; line: 2, column: 26]"
  },
  "status": 500
}

```

### See

[https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-track-total-hits.html#search-request-track-total-hits](https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-track-total-hits.html#search-request-track-total-hits)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 22, 2019, 1:25pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232/2 "2019-01-22T13:25:23Z")

</div>

@jimczi Could you look?

---

<div class="post-metadata">

**Author:** ![jimczi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimczi/32/47985_2.png) [@jimczi](https://discuss.elastic.co/u/jimczi)\
**Post date:** [January 22, 2019, 1:55pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232/3 "2019-01-22T13:55:09Z")

</div>

Thanks for testing the alpha2 release!  
This feature has been added after the release of 7.0.0-alpha2 so it is currently only in the master branch.  
and will be available in the next 7.0 release, the docs wrongly refer to 7.0.0-alpha2 but it contains new features that are only in master:

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

---

<div class="post-metadata">

**Author:** ![kzzzzo2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kzzzzo2/32/40077_2.png) [@kzzzzo2](https://discuss.elastic.co/u/kzzzzo2)\
**Post date:** [January 22, 2019, 2:21pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232/4 "2019-01-22T14:21:31Z")

</div>

Thanks @jimczi @dadoonet  
Looking forward to the next 7.0 release 😀

---

<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 19, 2019, 2:26pm UTC](https://discuss.elastic.co/t/track-total-hits-support-by-integer/165232/5 "2019-02-19T14:26:32Z")

</div>

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