[ https://issues.apache.org/jira/browse/LUCENE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111934#comment-17111934 ]
Mikhail Khludnev commented on LUCENE-9360: ------------------------------------------ bq. what the problem is with calling advance() under the hood, can you explain [~jpountz], it turns out like this: let's we have parents docnums:10,20,30. While scoring 10th block child filter might jump to behind 20th block due to absent child docs. And then {{ToParentDocValues.advanceExact(20)}} will drag child field doc values back. It never happens in {{/master}} nor {{_8x}} now, but attempting to reuse docVals across Sorting Group Heads lead to this trouble. LUCENE-9328 provides a fix for it, but it a little bit fragile. Really appreciate your feedback. Thanks. > might be NEEDED. ToParentDocValues uses advanceExact() of underneath DocValues > ------------------------------------------------------------------------------ > > Key: LUCENE-9360 > URL: https://issues.apache.org/jira/browse/LUCENE-9360 > Project: Lucene - Core > Issue Type: Sub-task > Reporter: Mikhail Khludnev > Priority: Major > > Currently {{ToParentDocvalues.advanceExact()}} propagates it to > {{DocValues.advance()}} as advised at LUCENE-7871. It causes some problem at > LUCENE-9328 and seems not really reasonable. The later jira has patch > attached which resolves this. The questions is why(not)? > cc [~jpountz] -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org