# Multi Core types mapping with a single field

**URL:** <https://discuss.elastic.co/t/multi-core-types-mapping-with-a-single-field/13536>\
**Category:** Elasticsearch\
**Created:** [September 10, 2013, 12:04pm UTC](https://discuss.elastic.co/t/multi-core-types-mapping-with-a-single-field/13536 "2013-09-10T12:04:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Asad\_Naqvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asad_naqvi/32/2117_2.png) [@Asad\_Naqvi](https://discuss.elastic.co/u/Asad_Naqvi)\
**Post date:** [September 10, 2013, 12:04pm UTC](https://discuss.elastic.co/t/multi-core-types-mapping-with-a-single-field/13536/1 "2013-09-10T12:04:03Z")

</div>

Greetings,  
e are running into a scenario where we get json documents from a third  
party website and consume it in our elastic search index for search  
purpose. Consider the following mapping example and please excuse brevity  
for simplicity:  
{  
"type1":{  
"properties":{  
"Value":{"type":"string"}  
}  
}  
}  
but now value field is returning string values some times and sometimes it  
will return array of values.like:  
{  
"type1":{  
"properties":{  
"Value":{  
"properties":{  
"attrId":{"type":"long"},  
"format Value":{"type":"string"}  
}  
}  
}  
}  
}

Is there any discussion already going on?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\
**Post date:** [September 10, 2013, 4:53pm UTC](https://discuss.elastic.co/t/multi-core-types-mapping-with-a-single-field/13536/2 "2013-09-10T16:53:23Z")

</div>

If the question is whether you can have the same field appearing on the  
index with different types at the same time (e.g. string or object), the  
answer is no 🙂  
The best solution would be to just use different names.

Hope this helps  
Luca

On Tuesday, September 10, 2013 2:04:03 PM UTC+2, Asad Naqvi wrote:

> Greetings,  
> e are running into a scenario where we get json documents from a third  
> party website and consume it in our Elasticsearch index for search  
> purpose. Consider the following mapping example and please excuse brevity  
> for simplicity:  
> {  
> "type1":{  
> "properties":{  
> "Value":{"type":"string"}  
> }  
> }  
> }  
> but now value field is returning string values some times and sometimes it  
> will return array of values.like:  
> {  
> "type1":{  
> "properties":{  
> "Value":{  
> "properties":{  
> "attrId":{"type":"long"},  
> "format Value":{"type":"string"}  
> }  
> }  
> }  
> }  
> }
> 
> Is there any discussion already going on?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:17am UTC](https://discuss.elastic.co/t/multi-core-types-mapping-with-a-single-field/13536/3 "2017-07-06T02:17:15Z")

</div>