I've been reading up on parent/child relationships and had a couple
questions:
On the Practical Considerations
http://www.elastic.co/guide/en/elasticsearch/guide/current/parent-child-performance.html
page, it's suggested that you should "Use parent-child relationships
sparingly, and only when there are many more children than parents." Is
there a particular ratio of parent to children where the parent/child
approach is better than using the nested type? What about if the number of
children per parent varies widely (zero to upwards of 100 children).
If I have a structure like :
{
"Company" : {
"Company_id" : {
"type": "integer"
},
"Company_tx" : {
"type" : "string"
}
"Deal_Companies" : {
"type" : "nested",
"properties" : {
"geocode": {
"type" : "geo_point"
},
"DealRole" : {
"type" : "string" // possible values: "Buyer, Seller, Broker"
},
"LegalEntityName" : {
"type" : "string"
}
}
}
}
}
The idea is that a single company can have multiple legal entity names.
Things I would want to know are how often that company was a buyer, seller,
or broker and in what part of the country they were doing business in.
Using aggregations, would I be able to answer questions like that?
Thanks!
--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0bad5dd7-fe5a-4bfd-8158-a411e5a40887%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.