# What is the difference in having my own type field in the document vs using \_type in elastic search? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 2, 2017, 12:44pm UTC](https://discuss.elastic.co/t/what-is-the-difference-in-having-my-own-type-field-in-the-document-vs-using--type-in-elastic-search/73677 "2017-02-02T12:44:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Atul\_Bagga](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_bagga/32/15047_2.png) [@Atul\_Bagga](https://discuss.elastic.co/u/Atul_Bagga)\ **Post date:** [February 2, 2017, 12:44pm UTC](https://discuss.elastic.co/t/what-is-the-difference-in-having-my-own-type-field-in-the-document-vs-using--type-in-elastic-search/73677/1 "2017-02-02T12:44:46Z")
I have two types of documents they are different in some fields and have some common fields. I am adding an additional field called type to differentiate between the two since i want to give different boosts to different fields depending on the type. What is the difference in using my type field (as explained above) vs \_type fields of Elastic search? My understanding is there is no difference as far as underlying Lucene storage is concerned since \_type is a elastic search concept and lucene doesn't know about it. But are there any pros cons of using one approach over another? Note: The two types of documents I have share a parent child relationship or sorts. Is there something better I could do to store them besides just using a type field? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 2, 2017, 12:44pm UTC](https://discuss.elastic.co/t/what-is-the-difference-in-having-my-own-type-field-in-the-document-vs-using--type-in-elastic-search/73677/2 "2017-03-02T12:44:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.