# What happened to multifield from 0.9 -\> 1.0?

**URL:** <https://discuss.elastic.co/t/what-happened-to-multifield-from-0-9-1-0/19649>\
**Category:** Elasticsearch\
**Created:** [September 5, 2014, 7:33pm UTC](https://discuss.elastic.co/t/what-happened-to-multifield-from-0-9-1-0/19649 "2014-09-05T19:33:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_Treher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justin_treher/32/45243_2.png) [@Justin\_Treher](https://discuss.elastic.co/u/Justin_Treher)\
**Post date:** [September 5, 2014, 7:33pm UTC](https://discuss.elastic.co/t/what-happened-to-multifield-from-0-9-1-0/19649/1 "2014-09-05T19:33:57Z")

</div>

Apparently I have left a serious bug in my searches. We upgraded from 0.9  
to 1.0.1 some time ago.

I changed all the multi\_fields to the new format, where I put "type" :  
"string" instead of "multi\_field." As documented here:  
[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/\_multi\_fields.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_multi_fields.html)

# Now they look like this

"bag\_holder":{  
"type":"string"  
, "path" : "just\_name"  
, "fields":{  
"bag\_holder" : {"type":"string", "analyzer":"custom"}  
,"bag\_holder\_booster" : {"type":"string", "analyzer":"keyword\_booster"}  
}  
}

However, I kept the "path" : "just\_name" and left my other fields as they  
were according the to information provided in the link above. The problem,  
as with the example above, is that my "field with the same name as  
property" must now be accessed in the query as item.item rather than just  
item as before. So, what's happening is that my queries are running the  
default analyzers for "item" by itself. Is there better documentation for  
converting? I want to verify that the only fix I need here is just to move  
all the attributes out of the "same name" field and put them directly under  
the property. Anything additional will just remain in the fields area.

# The Fix ??

"bag\_holder":{  
"type":"string"  
, "path" : "just\_name" (I know this is "optional" and deprecated")  
, "analyzer":"custom"  
, "fields":{  
"bag\_holder\_booster" : {"type":"string", "analyzer":"keyword\_booster"}  
}  
}

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/dd8d8126-a3bf-4619-871a-f71912aab211%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dd8d8126-a3bf-4619-871a-f71912aab211%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:04am UTC](https://discuss.elastic.co/t/what-happened-to-multifield-from-0-9-1-0/19649/2 "2017-07-06T01:04:01Z")

</div>

Closed on July 6, 2017, 1:04am UTC