[
https://issues.apache.org/jira/browse/SOLR-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-4877:
--------------------------------
Attachment: SOLR-4877.patch
Simple patch for getDocSetNC().
I am not sure why there is this special handling of TermQuery, in my opinion,
the if colause should go away and Solr should call the default
TermScorer#collect(). There is nbo reason to have a special handling here (and
no performance impact as TermScorer#collect is implemented the same way).
We should remove the special case here, any comments?!
> 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
> Attachments: 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,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.
--
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]