On http://www.elasticsearch.org/guide/reference/mapping/ there is a
reference to the schemaless nature of ES and its ability to guess
field types. But how exactly does it guess? Does it try to create
instances of Java types like Date, Integer, Float, Boolean, String,
etc.? Or does it use some heuristic based on field names (there is an
example of "first_name" at the above URL, for example)?
Json already have numeric types and boolean types, so those are used based
on it. Date types are automatically detected if the string matches
predefined (though configurable) date formats (more info here: Elasticsearch Platform — Find real-time answers at scale | Elastic).
On Elasticsearch Platform — Find real-time answers at scale | Elastic there is a
reference to the schemaless nature of ES and its ability to guess
field types. But how exactly does it guess? Does it try to create
instances of Java types like Date, Integer, Float, Boolean, String,
etc.? Or does it use some heuristic based on field names (there is an
example of "first_name" at the above URL, for example)?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.