Timothy Potter created SOLR-7866:
------------------------------------

             Summary: getMaxVersionFromIndex is throwing an NPE if some 
segments are not current
                 Key: SOLR-7866
                 URL: https://issues.apache.org/jira/browse/SOLR-7866
             Project: Solr
          Issue Type: Bug
            Reporter: Timothy Potter
            Assignee: Timothy Potter
            Priority: Blocker
             Fix For: 5.3


Reported by user on #solr irc (via Shalin)
{code}
java.lang.NullPointerException
        at 
org.apache.lucene.util.NumericUtils.prefixCodedToLong(NumericUtils.java:226)
        at org.apache.lucene.util.NumericUtils.getMaxLong(NumericUtils.java:582)
        at 
org.apache.solr.update.VersionInfo.getMaxVersionFromIndex(VersionInfo.java:234)
        at 
org.apache.solr.update.UpdateLog.seedBucketsWithHighestVersion(UpdateLog.java:1580)
        at 
org.apache.solr.update.UpdateLog.seedBucketsWithHighestVersion(UpdateLog.java:1610)
        at org.apache.solr.core.SolrCore.seedVersionBuckets(SolrCore.java:861)
        at org.apache.solr.core.SolrCore.<init>(SolrCore.java:843)
        at org.apache.solr.core.SolrCore.<init>(SolrCore.java:658)
        at org.apache.solr.core.CoreContainer.create(CoreContainer.java:637)
        at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:381)
        at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:375)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$1.run(ExecutorUtil.java:148)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to