Elasticsearch Cannot Change Field Mapping: Reindex Guide

How to fix it

Try these in order — the most common fix is first.

1. 1. Inspect the mapping

   Copy steps
   1. GET <index>/_mapping and the field capabilities API to confirm the type
   2. Use the analyze API to see how text is tokenized
   Did this fix it? Yes No

2. 2. Reindex into a new index

   Copy steps
   1. Create a new index with the corrected mapping
   2. POST _reindex from the old index to the new one
   3. Switch an alias to the new index, then delete the old one
   Did this fix it? Yes No

3. 3. Prevent a repeat

   Copy steps
   1. Define explicit mappings in an index template
   2. Disable or restrict dynamic mapping
   Did this fix it? Yes No

Symptoms

Mapping update rejected, or document indexing fails with mapper_parsing_exception because a value does not match the field type.

Why it happens

• Dynamic mapping guessed the wrong type from the first document
• Different sources send different types for the same field
• Field type changed upstream

This guide also covers

• elasticsearch mapper_parsing_exception
• elasticsearch change field type
• elasticsearch mapping conflict

Other Elasticsearch errors

• Elasticsearch Cluster Health Yellow: Causes and Fixes
• Elasticsearch Cluster Health Red: How to Fix It
• Elasticsearch Unassigned Shards: Why and How to Fix
• Elasticsearch circuit_breaking_exception: Data Too Large
• Elasticsearch High JVM Memory Pressure and Out of Memory
• Elasticsearch Disk Watermark: Index Read-Only (FORBIDDEN/12)
• Elasticsearch Limit of Total Fields [1000] Exceeded
• Why Is Elasticsearch So Slow? Fixing Slow Searches