[
https://issues.apache.org/jira/browse/LUCENE-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520089#comment-15520089
]
Alexandre Rafalovitch commented on LUCENE-7452:
-----------------------------------------------
I was trying to think of a better way to phrase it, but could not. And - after
a bit of sentence parsing - users should be able to figure out how to isolate
the issue. It may also be useful to have a blog post or something demonstrating
it. I'll try to write one when I have some free time.
> 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
> Assignee: Mikhail Khludnev
> Priority: Minor
> Fix For: master (7.0), 6.3
>
> 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
