# Elasticsearch 2.1.1 with \_type not indexed

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092>\
**Category:** Elasticsearch\
**Created:** [January 26, 2016, 7:01am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092 "2016-01-26T07:01:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![wq\_Huang](https://avatars.discourse-cdn.com/v4/letter/w/858c86/32.png) [@wq\_Huang](https://discuss.elastic.co/u/wq_Huang)\
**Post date:** [January 26, 2016, 7:01am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092/1 "2016-01-26T07:01:46Z")

</div>

Hi,

I am using es 2.1.1+kibana 4.3.1, the \_type fields is not indexed as kibana shown,thus I can not do search or filter by \_type.The official doc says es will index it by default and the \_type field is no longer configurable...How can I solve that ?

**Here is what kibana shows:**  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/0/025435b9671d765e671409744ba533dc866e1714.jpg)

**Here is what happened when I tried to configure \_type manually:**  
**{"error":{"root\_cause":[{"type":"mapper\_parsing\_exception","reason":"\_type is not configurable"}],"type":"mapper\_parsing\_exception","reason":"Failed to parse mapping [_default_]: \_type is not configurable","caused\_by":{"type":"mapper\_parsing\_exception","reason":"\_type is not configurable"}},"status":400}**

---

<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 26, 2016, 7:16am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092/2 "2016-01-26T07:16:15Z")

</div>

If you need to filter a document by type, it means to me that type is an important data for you.  
I'd add a type field in my docs then instead of relying on technical metadata fields.

---

<div class="post-metadata">

**Author:** ![johncollaros](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johncollaros/32/7613_2.png) [@johncollaros](https://discuss.elastic.co/u/johncollaros)\
**Post date:** [February 4, 2016, 11:01am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092/3 "2016-02-04T11:01:53Z")

</div>

Hi,

\_type is indexed. But it seems because they have removed the ability to configure settings for \_type, it also has removed the information from the \_mapping API. Kibana relies on this to be able to know if a field is indexed or not.

A workaround is to edit the setting in the .kibana data itself.

There is more info posted here:  
[https://discuss.elastic.co/t/elasticsearch-2-0-with--type-not-indexed/35244/18?u=johncollaros&source\_topic\_id=40092](https://discuss.elastic.co/t/elasticsearch-2-0-with--type-not-indexed/35244/18?u=johncollaros&source_topic_id=40092)

I have updated the kibana issue, and created an issue in elasticsearch issue tracker, both are linked in there.

With the workaround, I have been able to once again filter on \_type.  
I never bother indexing type separately, there is no need. That is what \_type is for, and as the docs tell you, it is indexed and it is required to be indexed for performance reasons.

Hope this helps.

---

<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, 11:18pm UTC](https://discuss.elastic.co/t/elasticsearch-2-1-1-with--type-not-indexed/40092/4 "2017-07-05T23:18:57Z")

</div>