[
https://issues.apache.org/jira/browse/SOLR-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-4877:
--------------------------------
Description:
In LUCENE-5023 it was reported that composite reader contexts should not
contain null fields() readers. But this is wrong, as a null-fields() reader may
contain documents, just no fields.
fields() and terms() is documented to return null, so DocSets should check for
null (like all queries do in Lucene). It seems that DocSetNC does not correctly
check for null.
was:
In LUCENE-5023 it was reported that composite reader contexts should not
contain null fields() readers. But this is wrong, as a null-fields() reader may
contain documents,m just no fields.
fields() is documented to contain null fields, so DocSets should check for null
(like all fields do in Lucene). It seems that DocSetNC does not correctly check
for null.
> SolrIndexSearcher#getDocSetNC should check for null return in
> AtomicReader#fields()
> -----------------------------------------------------------------------------------
>
> Key: SOLR-4877
> URL: https://issues.apache.org/jira/browse/SOLR-4877
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.2, 4.3
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Attachments: SOLR-4877-nospecialcase.patch, SOLR-4877.patch
>
>
> In LUCENE-5023 it was reported that composite reader contexts should not
> contain null fields() readers. But this is wrong, as a null-fields() reader
> may contain documents, just no fields.
> fields() and terms() is documented to return null, so DocSets should check
> for null (like all queries do in Lucene). It seems that DocSetNC does not
> correctly check for null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
