Index time boosting in Elastic search version 2

Elastic Stack Elasticsearch
1

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.

2

Yes. It's not. Did not you find it in breaking change or when using the migration plugin?

3

I did not see it in the breaking changes. But did not try the plugin yet.

4

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

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

Not sure if your issue comes from that.

5

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"
}
}
},

6

Yes.

That said why not indexing directly in a cluster already in 2.0 instead of reindexing in 1.x then upgrade?

7

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.