Is anyone thinking this is a normal behavior? To get random children? And to have a different (correct) behavior if you commit after sending each document?
Fabien -----Original Message----- From: Fabien Renaud [mailto:fabien.ren...@findwise.com] Sent: den 24 januari 2017 19:23 To: solr-user@lucene.apache.org Subject: RE: Indexing nested documents giving back unrelated parents when asking for children But the problem is already there with only two levels. If I change the code to add document to Solr by the following: client1.add(doc1); client1.commit(); client1.add(doc4); client1.commit(); Then things work as expected as I get the follwing result (as well as the correct parent-child relation between 1,2 and 4;5): "docs": [ { "id": "2" }, { "id": "5" } ] Fabien -----Original Message----- From: Mikhail Khludnev [mailto:gge...@gmail.com] Sent: den 24 januari 2017 19:02 To: solr-user <solr-user@lucene.apache.org> Subject: RE: Indexing nested documents giving back unrelated parents when asking for children Fabien, Giving this you have three levels can you update the sample code accordingly? I might already replied on such question earlier, iirc filter should enumerate all types beside of the certain one. 24 янв. 2017 г. 16:21 пользователь "Fabien Renaud" < fabien.ren...@findwise.com> написал: I know it works as expected when I set type_s:up as you describe. But I was expecting no children at all in my query. In my real query I have a document with several children and thus can't specify a specific type with childFilter. And I can't give back all children because some of them do not make any sense at all. And the problem appears for an intermediate node (which has children and which itself a child of another). Fabien -----Original Message----- From: Mikhail Khludnev [mailto:m...@apache.org] Sent: den 24 januari 2017 14:06 To: solr-user <solr-user@lucene.apache.org> Subject: Re: Indexing nested documents giving back unrelated parents when asking for children Hello Fabien, I believe parentFilter should be type_s:up, and consequently the type_s:up should go in fq. On Tue, Jan 24, 2017 at 3:30 PM, Fabien Renaud <fabien.ren...@findwise.com> wrote: > Hello, > > I'm wondering if I missed something in my code (which uses solrj 6.3): > > public class Main { > > private SolrClient client1; > > public void run() { > client1 = new > HttpSolrClient.Builder("http://localhost:8983/solr > ").build(); > > SolrInputDocument doc1 = new SolrInputDocument(); > > doc1.addField("id", "1"); > doc1.addField("type_s", "up"); > SolrInputDocument doc2 = new SolrInputDocument(); > > doc2.addField("id", "2"); > doc2.addField("type_s", "down"); > > doc1.addChildDocument(doc2); > > SolrInputDocument doc4 = new SolrInputDocument(); > doc4.addField("id", "4"); > doc4.addField("type_s", "up"); > > SolrInputDocument doc5 = new SolrInputDocument(); > doc5.addField("id", "5"); > doc5.addField("type_s", "down"); > > doc4.addChildDocument(doc5); > > try { > client1.add("techproducts", Arrays.asList(doc1,doc4)); > } catch (Exception e) { > System.out.println("Indexing failed" + e); > } > } > > If I start Solr 6.3 using bin/start start -e techproduct and ask the > following: > > http://localhost:8983/solr/techproducts/select?fl=*,[ > child%20parentFilter=type_s:down]&fq=type_s:down&indent=on&q=*:*&wt=js > on > > > then I get: > > { > "docs": [ > { > "id": "2", > "type_s": "down" > }, > { > "id": "5", > "type_s": "down", > "_childDocuments_": [ > { > "id": "1", > "type_s": "up" > } > ] > } > ] > } > > which seems to be a bug for me. Or did I miss something? > Notice that the relations "2 is a child of 1" and "5 is a child of 4" > are working fine. It's just that I get extra (unwanted and unrelated) relations. > > Notice that at some point I manage to get back two documents with the > __same__ id (with different version). I'm not able to reproduce this > but I guess it could be related. > > Fabien > > -- Sincerely yours Mikhail Khludnev
