Rick Leir-2 wrote
> Yes! And the join queries get complicated. Yonick has some good blogs on
> this.
>
> On May 19, 2017 11:05:52 AM EDT, biplobbiswas <
> revolutionisme+solr@
> > wrote:
>>Wait, if I understand correctly, the documents would be indexed like
&g
Wait, if I understand correctly, the documents would be indexed like that but
we can get back the document as nested if we perform the
blockjoinqueryparsing?
So if I query normally with the default parser I would get all documents
separately?
Did i understand correctly?
Thanks & regards
Biplob
Hi
Mikhail Khludnev-2 wrote
> Hello,
>
> You need to use
> https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-BlockJoinQueryParsers
> and
> https://cwiki.apache.org/confluence/display/solr/Transforming+Result+Documents#TransformingResultDocuments-[child]-ChildDocTransform
Update,
I checked with the following example as well and this also flattens the
results.
I took the example from here -
https://issues.apache.org/jira/browse/SOLR-1945
package com.airplus.poc.edl.spark.auditeventindexer;
import java.io.IOException;
import org.apache.solr.client.solrj.SolrServe
I have the following structure for the class used for indexing a solr
document. I am using solrj 5.5.2 (same solr is being used on the cluster
with the collection in solr cloud mode having 3 shards)
I added the @Field(child = true) to the ChnagedAttribute object and even
though my document is inde
