'Elasticsearch - Want to sort by field in all indices where that particular field available or not if not then avoid it

Currently, Getting result based on scoring but what i want to do is i want a result based on scoring + Field Status with value true/false.

If value is true then needed that results in priority but there is possibility that status field is not exist in all indices.

           "query" => [
                  'bool' => [
                     'filter' => $filter,
                     'must' => [
                     "multi_match" => [
                        'query' => "$string",
                        "type" => "cross_fields",
                        'fields' => ['field1','field2','field3'],
                        "minimum_should_match" => "80%"
                         ]
                    ]
                  ]
            ],
            "sort" => [
                    "_score",
                    [ "status" => ["order" => "desc","unmapped_type" => "boolean"] ]
            ],

But getting error below :

[type] => illegal_argument_exception
[reason] => Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [status] in order to load field data by uninverting the inverted index. Note that this can use significant memory.

Anyone help me out to ignore for indices where that field not available or any other solution with this problem?



Solution 1:[1]

As discussed in the chat, the issue happened due to @jilesh

forget to delete the old index mapping and only upate the data that's what this thing was occurring.

Below answer is relevant when you get below error with proper setup

Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [status] in order to load field data by uninverting the inverted index. Note that this can use significant memory.

In that case, please enable the field data on the field if you want to get rid of the error but beware it can cause performance issues.

Read more about the field data on official site.

You can enable it in your order field in your mapping as shown.

{
  "properties": {
    "order": { 
      "type":     "text",
      "fielddata": true
    }
  }
} 

Solution 2:[2]

works for me

curl -X PUT -H "Content-Type: application/json" \
    -d '{"properties": {"format": { "type":"text","fielddata": true}}}' \
    <your_host>:9200/<your_index>/_mapping

Solution 3:[3]

In my case, I had to use the aggregatable {fieldname}.keyword field. Here's an example using Nest .NET.

.Sort(s => s
    .Ascending(f => f.Field1.Suffix("keyword"))
    .Ascending(f => f.Field2.Suffix("keyword"))
    .Ascending(f => f.Field3.Suffix("keyword")))

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1
Solution 2 Adán Escobar
Solution 3 Bertm13