[ 
https://issues.apache.org/jira/browse/LUCENE-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670077#comment-13670077
 ] 

Uwe Schindler edited comment on LUCENE-5023 at 5/30/13 5:52 AM:
----------------------------------------------------------------

This is not a bug in ReaderContext. If an atomic reader has no fields it is 
perfectly fine to return null (it is documented like that). The bug is 
somewhere else in Solr or your own code. It must be listed in the reader 
context, as it may contain documents.
                
      was (Author: thetaphi):
    This is not a bug in ReaderContext. If a composite reader has no fields it 
is perfectly fine to return null (it is documented like that). The bug is 
somewhere else in Solr or your own code. It must be listed in the reader 
context, as it may contain documents.
                  
> Only reader that contains fields can be added into readerContext
> ----------------------------------------------------------------
>
>                 Key: LUCENE-5023
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5023
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 4.2
>            Reporter: Bao Yang Yang
>            Assignee: Uwe Schindler
>            Priority: Critical
>              Labels: patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When there is only Segements in solr core, which means no any indexes, in 
> CompositeReaderContext.build() method, the atomicReader that has no fields 
> returned should not be added into leaves. Otherwise, in 
> SolrIndexSearcher.getDocSetNC(Query query, DocSet filter), when execute line 
> fields.terms(t.field()), a nullpointerexception will occur since fields 
> variable is 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]

Reply via email to