How to fix QueryShardException: No mapping found for [field] in order to sort on in Elasticsearch

ElasticsearchINTERMEDIATEMEDIUMUpdated Dec 22, 2025· 193 views

This error occurs when attempting to sort by a field that has no mapping defined in the Elasticsearch index. The field either doesn't exist, hasn't been indexed yet, or is defined as a text type which cannot be used for sorting.

Quick fix

Fixes QueryShardException: No mapping found for [field] in order to sort on

GET /your-index/_mapping
  1. Verify the field exists in your index mapping
  2. Use the unmapped_type parameter to handle missing fields
  3. Add explicit mapping for the field
  4. Use the keyword subfield for text fields
elasticsearch — error
GET /your-index/_mapping
QueryShardException: No mapping found for [field] in order to sort on

What this error means

Elasticsearch throws this QueryShardException when you attempt to sort search results by a field that doesn't have a mapping in the index. Mappings in Elasticsearch define the data type and structure of fields, and sorting requires Elasticsearch to know the field's type to properly order results. This error typically appears in three scenarios: the field was never mapped because no documents containing it have been indexed yet, the field name is misspelled in your sort query, or the field is mapped as a text type rather than a sortable type like keyword or numeric. Text fields are analyzed and broken into tokens for full-text search, making them unsuitable for sorting operations that require exact field values. The error message will indicate which specific field caused the problem, helping you identify whether it's a mapping issue, a query typo, or a type mismatch between what you're trying to sort and how the field is actually defined.

Typical symptoms

  • Search queries fail with QueryShardException when sort parameter is included
  • Error message specifies the exact field name that lacks mapping
  • Query works fine when sort clause is removed
  • Error occurs after index creation but before any documents are indexed
  • Sorting works on some indices but fails on others with same query

Common causes

  1. Field specified in sort query has never been mapped because no documents containing it exist in the index
  2. Field name in sort query is misspelled or doesn't match the actual field name in documents
  3. Field is mapped as text type instead of keyword, numeric, or date type suitable for sorting
  4. Sorting on a multi-index query where the field doesn't exist in all targeted indices
  5. Dynamic mapping is disabled and field was never explicitly defined in index mapping

How to fix "QueryShardException: No mapping found for [field] in order to sort on"

1Verify the field exists in your index mapping

Check if the field you're trying to sort on actually exists in your index mapping:

bash
GET /your-index/_mapping

Look for the field name in the response. If it's not present, the field hasn't been mapped yet. If you're sorting across multiple indices, check each one:

bash
GET /index1,index2/_mapping/field/your-field-name

This will show you whether the field exists in each index and how it's mapped.

2Use the unmapped_type parameter to handle missing fields

If the field doesn't exist in some indices but you still want the query to work, use the unmapped_type parameter to tell Elasticsearch how to treat unmapped fields:

json
GET /your-index/_search
{
  "query": {
    "match_all": {}
  },
  "sort": [
    {
      "your-field": {
        "order": "desc",
        "unmapped_type": "long"
      }
    }
  ]
}

For keyword fields, use "unmapped_type": "keyword". For dates, use "unmapped_type": "date". This tells Elasticsearch to treat documents in indices without this field as if they have no value for it, rather than failing the query.

3Add explicit mapping for the field

If the field should exist but doesn't, add it to your index mapping. For a new index:

json
PUT /your-index
{
  "mappings": {
    "properties": {
      "your-field": {
        "type": "keyword"
      }
    }
  }
}

For existing indices, you can add new fields to the mapping:

json
PUT /your-index/_mapping
{
  "properties": {
    "your-field": {
      "type": "keyword"
    }
  }
}

Choose the appropriate type: keyword for exact-value sorting, long/integer for numbers, date for timestamps. Never use text for fields you need to sort on.

4Use the keyword subfield for text fields

If you're trying to sort on a text field, you cannot sort on the analyzed text directly. Most text fields have a .keyword subfield created automatically for sorting and aggregations:

json
GET /your-index/_search
{
  "query": {
    "match_all": {}
  },
  "sort": [
    {
      "your-field.keyword": {
        "order": "asc"
      }
    }
  ]
}

Check your mapping to confirm the .keyword subfield exists. If it doesn't, you can add it:

json
PUT /your-index/_mapping
{
  "properties": {
    "your-field": {
      "type": "text",
      "fields": {
        "keyword": {
          "type": "keyword",
          "ignore_above": 256
        }
      }
    }
  }
}
5Reindex if mapping changes require it

If you've corrected the mapping but documents were already indexed with incorrect types, you need to reindex:

json
POST /_reindex
{
  "source": {
    "index": "your-old-index"
  },
  "dest": {
    "index": "your-new-index"
  }
}

Then use an index alias to switch from the old to new index without downtime:

json
POST /_aliases
{
  "actions": [
    { "remove": { "index": "your-old-index", "alias": "your-alias" } },
    { "add": { "index": "your-new-index", "alias": "your-alias" } }
  ]
}

This ensures all documents are properly indexed according to the corrected mapping.

Advanced notes

When working with multi-index queries (using wildcards or multiple index names), remember that Elasticsearch checks all targeted indices for field mappings. If any index is missing the field, use unmapped_type to prevent query failures.

For optimal sorting performance, avoid text fields entirely. Text fields are analyzed into tokens, making them memory-intensive and slow for sorting. Always use keyword, numeric, or date types for fields you'll sort or aggregate on.

If you're using dynamic mapping and want to ensure certain fields are always mapped correctly, create index templates that define mappings for field patterns:

json
PUT /_index_template/your-template
{
  "index_patterns": ["logs-*"],
  "template": {
    "mappings": {
      "properties": {
        "timestamp": { "type": "date" },
        "status": { "type": "keyword" },
        "message": {
          "type": "text",
          "fields": {
            "keyword": { "type": "keyword", "ignore_above": 256 }
          }
        }
      }
    }
  }
}

This ensures new indices matching the pattern automatically get proper mappings without manual intervention.

In Elasticsearch 7.x and later, the unmapped_type parameter is particularly important when dealing with index patterns that might include indices created at different times or with different schemas. It allows queries to be more resilient to mapping variations across indices.

Frequently asked questions

What does "QueryShardException: No mapping found for [field] in order to sort on" mean?
Elasticsearch throws this QueryShardException when you attempt to sort search results by a field that doesn't have a mapping in the index. Mappings in Elasticsearch define the data type and structure of fields, and sorting requires Elasticsearch to know the field's type to properly order results. This error typically appears in three scenarios: the field was never mapped because no documents containing it have been indexed yet, the field name is misspelled in your sort query, or the field is mapped as a text type rather than a sortable type like keyword or numeric.
How do I fix "QueryShardException: No mapping found for [field] in order to sort on"?
This error occurs when attempting to sort by a field that has no mapping defined in the Elasticsearch index. The field either doesn't exist, hasn't been indexed yet, or is defined as a text type which cannot be used for sorting.
What causes "QueryShardException: No mapping found for [field] in order to sort on"?
Field specified in sort query has never been mapped because no documents containing it exist in the index Field name in sort query is misspelled or doesn't match the actual field name in documents Field is mapped as text type instead of keyword, numeric, or date type suitable for sorting
Is the "QueryShardException: No mapping found for [field] in order to sort on" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading