Probably if you are interested in a many-to-many relation, you could be interested in the query time join. it has been the first type of join integrated in Solr. It allow you to avoid redundancies. It's slower than block join, but it doesn't force you to any specific indexing approach. It became less and less popular but there are scenario could be useful !
Take a look to Siren as well, it could be interesting, not sure it will help you as Siren will duplicate nested documents. Cheers On 29 January 2016 at 15:32, Jack Krupansky <jack.krupan...@gmail.com> wrote: > If you wish to change, add, or delete a child or change the parent you must > do an add of the entire block again with both the parent and all children. > This is because the efficiency of Block Join comes from the documents being > adjacent in Lucene and segments are immutable in Lucene, so the entire > block must be written to a new segment. > > > -- Jack Krupansky > > On Fri, Jan 29, 2016 at 5:13 AM, Sathyakumar Seshachalam < > sathyakumar_seshacha...@trimble.com> wrote: > > > Hi, > > > > Am trying to investigate the possibility of using Block Join query parser > > in a many-to-many relation scenario. > > Observation is that when a document is added as a child to more than one > > parent document (I use Solrj to do this), I seem to get two copies of the > > child document. Can this be avoided ? Is this per design ? > > Are there are articles talking about ways to model a many-to-many > > relationship (even if its a hacky solution). > > > > > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
