lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-7606) ToParentBlockJoinQuery fails with AIOOBE under certain circumstances
Date Sat, 30 May 2015 14:42:17 GMT


Yonik Seeley commented on SOLR-7606:

Seems like Lucene's implementation is overly constrained - it would be nice to just remove
all these checks that throw exceptions / assertions.

> ToParentBlockJoinQuery fails with AIOOBE under certain circumstances
> --------------------------------------------------------------------
>                 Key: SOLR-7606
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.10.4
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>         Attachments: LUCENE-6512.patch
> I had a customer using BlockJoin with Solr. He executed a block join query and the following
appeared in Solr's logs:
> {noformat}
> 28 May 2015 17:19:20  ERROR ( - java.lang.ArrayIndexOutOfBoundsException:
>         at org.apache.lucene.codecs.lucene40.BitVector.get(
>         at$BlockJoinScorer.nextDoc(
>         at$DefaultBulkScorer.scoreAll(
>         at$DefaultBulkScorer.score(
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at org.apache.solr.handler.component.QueryComponent.process(
>         at org.apache.solr.handler.component.SearchHandler.handleRequestBody(
>         at org.apache.solr.handler.RequestHandlerBase.handleRequest(
>         at org.apache.solr.core.SolrCore.execute(
>         at org.apache.solr.servlet.SolrDispatchFilter.execute(
>         at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
>         at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(
>         at org.apache.catalina.core.StandardWrapperValve.invoke(
>         at org.apache.catalina.core.StandardContextValve.invoke(
>         at org.apache.catalina.core.StandardHostValve.invoke(
>         at org.apache.catalina.valves.ErrorReportValve.invoke(
>         at org.apache.catalina.core.StandardEngineValve.invoke(
>         at org.apache.catalina.connector.CoyoteAdapter.service(
>         at org.apache.coyote.http11.Http11Processor.process(
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>         at$
>         at
> {noformat}
> I debugged this stuff and found out when this happens:
> The last block of documents was not followed by a parent. If one of the child documents
without a parent at the end of the index match the inner query, scorer calls nextSetBit()
to find next parent document. This returns -1. There is an assert afterwards that checks for
-1, but in production code, this is of course never executed.
> If the index has deletetions the false -1 is passed to acceptDocs and then triggers the
above problem.
> We should change the assert to another IllegalStateException() which is used to notify
the user if the orthogonality is broken. By that the user gets the information that his index
is broken and contains child documents without a parent at the very end of a segment.
> I have seen this on 4.10.4. Maybe thats already fixed in 5.0, but I just open this here
for investigation. This was clearly a problem in the index, but due to Solr's buggy implementation
of parent/child documents (you have to set the parent flag in contrast to Elasticsearch on
your own - which is stupid!!!) this was not detected at indexing time. We should open an issue
in Solr to fix this bad behaviour and make solr automatically add the parent field (it only
adds a "_root_" field automatically, maybe it should also add a "_parent_" field automatically).

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message