Fix MapperParsingException

✅ Solution

MapperParsingException usually arises from Elasticsearch trying to index a field with a data type inconsistent with its mapping (e.g., indexing text into a numeric field). To resolve this, either update the Elasticsearch mapping for the affected field to the correct data type using the `PUT index/_mapping` API or adjust the data being sent to match the existing mapping. If dynamic mapping is enabled, consider disabling it or defining explicit mappings to prevent Elasticsearch from inferring incorrect data types.