[
https://issues.apache.org/jira/browse/LUCENE-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated LUCENE-7452:
-------------------------------------
Attachment: LUCENE-7452.patch
What about this?
{panel}
java.lang.IllegalStateException: Child query must not match same docs with
parent filter. Combine them as must clauses (+) to find a problem doc.
docId=23, class org.apache.lucene.search.DisjunctionSumScorer
{panel}
{panel}
java.lang.IllegalStateException: Parent query must not match any docs beside
parent filter. Combine them as must (+) and must-not (-) clauses to find a
problem doc. docID=12
{panel}
> improve exception message: child query must only match non-parent docs, but
> parent docID=180314...
> --------------------------------------------------------------------------------------------------
>
> Key: LUCENE-7452
> URL: https://issues.apache.org/jira/browse/LUCENE-7452
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: 6.2
> Reporter: Mikhail Khludnev
> Priority: Minor
> Attachments: LUCENE-7452.patch
>
>
> when parent filter intersects with child query the exception exposes internal
> details: docnum and scorer class. I propose an exception message to suggest
> to execute a query intersecting them both. There is an opinion to add this
> suggestion in addition to existing details.
> My main concern against is, when index is constantly updated even SOLR-9582
> allows to search for docnum it would be like catching the wind, also think
> about cloud case. But, user advised with executing query intersection can
> catch problem documents even if they occurs sporadically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
