[ 
https://issues.apache.org/jira/browse/SOLR-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219312#comment-16219312
 ] 

ananthesh edited comment on SOLR-11517 at 10/25/17 7:19 PM:
------------------------------------------------------------

[~mkhludnev] Makes sense. We should be looking into this. Speaking about the 
indexing, we make sure childDocuments are always present

There is one more issue which we have found, which is reported here SOLR-11550. 
Not sure, both of them are related. We still need to debug on these issues


was (Author: antz):
[~mkhludnev] Makes sense. We should be looking into this.

There is one more issue which we have found, which is reported here SOLR-11550. 
Not sure, both of them are related. We still need to debug on these issues

> ToParentBlockJoinQuery fails when the parents/child fall in to different 
> segments
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-11517
>                 URL: https://issues.apache.org/jira/browse/SOLR-11517
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6.1
>            Reporter: ananthesh
>
> We have a system where all the documents in the collections are nested child 
> documents. We also have 'autoCommit' enabled for the collection. We also get 
> huge number of document updates. We found a scenario, where 'child' documents 
> were indexed in one segment, while 'parent' document got indexed in the other 
> segment. Here are the docid looks like
> 0 = 95638
> 1 = 95639
> 2 = 95640
> 3 = 272190 \{parent}
> Now if the solr request has been made using "parent" query parser like the 
> following
> {noformat}
> {!parent which=parent:true score=max}(...)
> {noformat}
> ToParentBlockJoinQuery which handles the request wont be able to find the 
> parent for the searched child documents. But if we trigger `optimize` for the 
> same index which forces to merge all the segments to single index, the above 
> request will be able to fetch the results. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to