# Mapper-size plugin query

**URL:** <https://discuss.elastic.co/t/mapper-size-plugin-query/54010>\
**Category:** Elasticsearch\
**Created:** [June 27, 2016, 8:35am UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010 "2016-06-27T08:35:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [June 27, 2016, 8:35am UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010/1 "2016-06-27T08:35:04Z")

</div>

Hi,  
I have started using the mapper-size plugin with one of our elasticsearch 2.2.0 clusters. In kibana I'm seeing that this field has a type of unknown and is unindexed. I've tried updating the mapping to:

"\_size": {  
"enabled": true,  
"type": "integer",  
"index": "not\_analyzed"  
},

...which throws an error:

"Mapping definition for [\_size] has unsupported parameters: [index : not\_analyzed]"

Removing the "index" parameter deals with that but still this field is not searchable. The plugin docs say this field is searchable so how can I fix this?

Regards,  
David

---

<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:** [June 27, 2016, 10:23am UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010/2 "2016-06-27T10:23:58Z")

</div>

`_size` is an integer. You don't need to define an analyzer.

It's automatically indexed and available for search as written in this example: [https://www.elastic.co/guide/en/elasticsearch/plugins/current/mapper-size-usage.html](https://www.elastic.co/guide/en/elasticsearch/plugins/current/mapper-size-usage.html)

You just have to set it with:

```auto
"_size": {
  "enabled": true
}

```

You probably have something else wrong and I think that you did not reindex your data, right?

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [June 27, 2016, 2:17pm UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010/3 "2016-06-27T14:17:31Z")

</div>

When I originally created added this field I did it as you have shown. As I'm doing this in a test environment I'm doing this against a newly created index.

As I say, the field is visible in kibana but the type is unknown and it is not searchable. So, given that the field is being calculated and displayed, it's not clear what I'm doing wrong. I've tried recreating the index, setting the type as integer and recreating the index pattern but it still displays in kibana as type "unknown".

---

<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:** [June 27, 2016, 2:31pm UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010/4 "2016-06-27T14:31:21Z")

</div>

Interesting. I would definitely move this thread to #kibana list and see what people says there.

---

<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:** [July 5, 2017, 10:40pm UTC](https://discuss.elastic.co/t/mapper-size-plugin-query/54010/5 "2017-07-05T22:40:11Z")

</div>