# Index time boosting in Elastic search version 2 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 13, 2015, 6:20am UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486 "2015-11-13T06:20:11Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mramaprasad](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mramaprasad](https://discuss.elastic.co/u/mramaprasad)\ **Post date:** [November 13, 2015, 6:20am UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/1 "2015-11-13T06:20:11Z")
I have a index time boost for a filed as follows in my mapping. "titlefield": { "type":"multi\_field", "fields":{ "title":{"type":"string","index":"analyzed", "store" : true}, "titleuntouched":{"type":"string","index":"not\_analyzed", "store" : true} }, "store":"yes", "boost":10 }, While adding this mapping I get "caused\_by":{"type":"mapper\_parsing\_exception","reason":"Mapping definition for [titlefield] has unsupported parameters: [boost : 10] [store : yes]"}},"status":400} Is boost at index time not allowed in version 2. ---
**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:** [November 13, 2015, 6:57am UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/2 "2015-11-13T06:57:42Z")
Yes. It's not. Did not you find it in breaking change or when using the migration plugin? ---
**Author:** ![mramaprasad](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mramaprasad](https://discuss.elastic.co/u/mramaprasad)\ **Post date:** [November 13, 2015, 3:38pm UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/3 "2015-11-13T15:38:40Z")
I did not see it in the breaking changes. But did not try the plugin yet. ---
**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:** [November 13, 2015, 3:57pm UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/4 "2015-11-13T15:57:45Z")
I'm sorry. Totally wrong here. You can use `boost` at index time. It's just not really recommended as not as flexible as boost at query time. [https://www.elastic.co/guide/en/elasticsearch/reference/current/index-boost.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-boost.html) So you are doing something wrong. Actually `multi_field` is still supported but you need to write it in a different way. Look at: [https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html) Not sure if your issue comes from that. ---
**Author:** ![mramaprasad](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mramaprasad](https://discuss.elastic.co/u/mramaprasad)\ **Post date:** [November 16, 2015, 10:35pm UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/5 "2015-11-16T22:35:57Z")
I think I will have to update the mapping to have the multi field that will be accepted by elasticcsearch 2. Add the new mapping and reindex data in version 1.1.1 in a different index than the one used by our production index. Then update to version to 2.0. The new multi field mapping is back ward compatible right? "creatorfield" : { "type" : "string", "fields": { "raw" : { "type": "string", "index": "not\_analyzed" } } }, ---
**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:** [November 17, 2015, 6:35am UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/6 "2015-11-17T06:35:56Z")
Yes. That said why not indexing directly in a cluster already in 2.0 instead of reindexing in 1.x then upgrade? ---
**Author:** ![mramaprasad](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mramaprasad](https://discuss.elastic.co/u/mramaprasad)\ **Post date:** [November 17, 2015, 4:10pm UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/7 "2015-11-17T16:10:56Z")
We are already live with elasticsearch 1.1.1. After installing 2 and reindexing data will take time and we can not be afford to do that. ---
**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:37pm UTC](https://discuss.elastic.co/t/index-time-boosting-in-elastic-search-version-2/34486/8 "2017-07-05T23:37:54Z")