You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/07/17 01:41:00 UTC
[jira] [Commented] (LUCENE-9999) CombinedFieldQuery can fail when
document is missing fields
[ https://issues.apache.org/jira/browse/LUCENE-9999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382400#comment-17382400 ]
ASF subversion and git services commented on LUCENE-9999:
---------------------------------------------------------
Commit f333b70dbff88c3670c73b7773f40b11e6712af3 in lucene's branch refs/heads/main from Jim Ferenczi
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=f333b70 ]
LUCENE-9999: CombinedFieldQuery can fail with an exception when document is missing fields (#185)
This change fixes a bug in `MultiNormsLeafSimScorer` that assumes that each
field should have a norm for every term/document.
As part of the fix, it adds validation that the fields have consistent norms
settings.
> CombinedFieldQuery can fail when document is missing fields
> -----------------------------------------------------------
>
> Key: LUCENE-9999
> URL: https://issues.apache.org/jira/browse/LUCENE-9999
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Julie Tibshirani
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> If some documents match but don't contain all fields, then {{CombinedFieldQuery}} can fail when attempting to compute norms. This is because {{MultiFieldNormValues}} assumes all fields in the document have norms.
> Originally surfaced in this Elasticsearch issue: https://github.com/elastic/elasticsearch/issues/74037.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org