elasticsearch version number: 5.6.14. This error has something to do with the ES version. You’d better explain the version number first so that some readers will not be invalid after operating according to my method

error mapping statement 1:

{
    "test_0904": {
        "mappings": {
            "user": {
                "properties": {
                    "birthday": {
                        "type": "date",
                        "store": true
                    },
                    "hobby": {
                        "type": "text",
                        "store": true
                    },
                    "id": {
                        "type": "long",
                        "store": true
                    },
                    "name": {
                        "type": "text",
                        "store": true
                    }
                }
            }
        }
    }
}

error mapping statement 2:

{
    "mappings": {
        "user": {
            "properties": {
                "birthday": {
                    "type": "date",
                    "store": true
                },
                "hobby": {
                    "type": "text",
                    "store": true
                },
                "id": {
                    "type": "long",
                    "store": true
                },
                "name": {
                    "type": "text",
                    "store": true
                }
            }
        }
    }
}

modified mapping statement:

{
    "properties": {
        "birthday": {
            "type": "date",
            "store": true
        },
        "hobby": {
            "type": "text",
            "store": true
        },
        "id": {
            "type": "long",
            "store": true
        },
        "name": {
            "type": "text",
            "store": true
        }
    }
}

To sum up, there are some differences in the structure of mapping statements supported by various versions of ES. Different versions have different statement writing methods. Some versions of parameters support and some versions do not support.

Read More:

• How to Solve Error: Missing type map configuration or unsupported mapping
• How to Solve Docker Error: elasticsearch exception: type=cluster_block_exception, reason=blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
• How to Solve elasticsearch root user start Error
• [Solved] ibatis.builder.BuilderException: Error parsing Mapper XML: Could not resolve type alias ‘XXX‘
• [Solved] Mybatis Error: Cause: org.apache.ibatis.builder.BuilderException: Error parsing SQL Mapper Configuration.
• This application has no explicit mapping for /error, so you are seeing this as a fallback.
• [Solved] This application has no explicit mapping for /error, so you are seeing this as a fallback
• Tk.mapper Common mapper Error: Error creating bean with name ‘commonMapper‘ defined in file xxx
• [Solved] elasticsearch Error: Failed: 1: this action would add [6] total shards, but this cluster currently has [2
• [Solved] target_link_libraries error: a missing vtable usually means the first non-inline virtual member function has no definition.
• [Maven Error] Exception in thread “main” java.lang.UnsupportedClassVersionError: org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
• [Solved] SpringBoot Error: This application has no explicit mapping for /error, so you are seeing this
• [Solved] Elasticsearch.service failed after enable elasticsearch security features
• [Solved] Whitelabel Error PageThis application has no explicit mapping for /error, so you are seeing this
• Conda create New environment Error: An unexpected error has occurred. Conda has prepared the above report.
• Parsing error in eslint parsing: unexpected token [How to Solve]
• [Solved] docker failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition
• Elasticsearch 6.2.3 version executes aggregation error Fielddata is disabled on text fields by default
• Android: Can’t create handler inside thread that has not called Looper.prepare() [Solved]
• [Solved] Kafka Start Log Error: WARN Found a corrupted index file due to requirement failed: Corrupt index found