CODEWITHSUNDEEP
elasticsearch
Slowacki
Slowacki

Reputation: 490

ElasticSearch - Upgraded indexed field to a Multi Field - new field is empty

Having noticed my sort on an indexed string field doesn't work properly, I've discovered that it's sorting analyzed strings so "bags of words" and if I want it to work properly I have to sort on the non-analyzed string. My plan was to just change the string field to a multi-field, using information I found in those two articles:

https://www.elastic.co/blog/changing-mapping-with-zero-downtime (Upgrade to a multi-field part) https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html

Using Sense I've created this field mapping

PUT myindex/_mapping/type
{
   "properties": {
      "Title": {
         "type": "string",
         "fields": {
            "Raw": {
               "type": "string",
               "index": "not_analyzed"
            }
         }
      }
   }
}

And then I try to sort my search results using the newly made field. I've put all of the name variations I could think of after reading the articles:

POST myindex/_search
{
    "_source" : ["Title","titlemap.Raw","titlemap.Title","titlemap.Title.Raw","Title.Title","Raw","Title.Raw"],
    "size": 6,
    "query": {
        "multi_match": {
            "query": "title",
            "fields": ["Title^5"
            ],
            "fuzziness": "auto",
            "type": "best_fields"
        }
    },
    "sort": {
        "Title.Raw": "asc"
    }
}

And that's what I get in response:

{
    "_index": "myindex_2015_11_26_12_22_38",
    "_type": "type",
    "_id": "1205",
    "_score": null,
    "_source": {
       "Title": "The title of the item"
    },
    "sort": [
       null
    ]
 }

Only the Title field's value is shown in the response and the sort criterium is null for every result.

Am I doing something wrong, or is there another way to do that?

Upvotes: 1

Views: 1017

Answers (1)

Val
Val

Reputation: 217474

The index name is not the same after re-indexing and thus the default mapping gets installed... that's probably why.

I suggest using an index template instead, so you don't have to care when to create the index and ES will do it for you. The idea is to create a template with the proper mapping you need and then ES will create every new index whenever it deems necessary, add the myindex alias and apply the proper mapping to it.

curl -XPUT localhost:9200/_template/myindex_template -d '{
  "template": "myindex_*",
  "settings": {
    "number_of_shards": 1
  },
  "aliases": {
     "myindex": {}
  },
  "mappings": {
    "type": {
      "properties": {
        "Title": {
          "type": "string",
          "fields": {
            "Raw": {
              "type": "string",
              "index": "not_analyzed"
            }
          }
        }
      }
    }
  }
}'

Then whenever you launch your re-indexing process a new index with a new name will be created BUT with the proper mapping and the proper alias.

Upvotes: 1

Related Questions