Restriction to a single shard seems like a big limitation for us.
Also, I was hoping that this was something Solr provided out of the box.
(Like
https://lucene.apache.org/solr/guide/6_6/updating-parts-of-documents.html#UpdatingPartsofDocuments-In-PlaceUpdates
)
Something like:
{
"id":"parents-id
If the document routing can be arranged such that the children and the
parent are always co-located in the same shard, and share an identifier,
the graph query can pull back the parent plus any arbitrary number of
"children" that have been added at any time in any order. In this scheme
"children" a
