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?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8a49e560-ce4b-4e8b-a2ed-ca610a25b92a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.