I mostly use the schemaless features of ElasticSearch.
But sometimes, I have a field that is typed as a String whereas it is in
fact the parent field of a parent/child relationship.
What is the best strategy to define those parent fields AND still use the
autogeneration of the schema by Elasticsearch?
I mostly use the schemaless features of Elasticsearch.
But sometimes, I have a field that is typed as a String whereas it is in
fact the parent field of a parent/child relationship.
What is the best strategy to define those parent fields AND still use the
autogeneration of the schema by Elasticsearch?
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.