[SOLR-9235] NPE when using non-numeric range query in deleteByQuery

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.0, 6.1
• Fix Version/s: 6.2
• Component/s: query parsers
• Assignee: Chris M. Hostetter
• Reporter: Anders Melchiorsen
• Created: 21/Jun/16 13:09
• Updated: 26/Aug/16 13:59
• Resolved: 05/Jul/16 21:37

Description

Upgrading from Solr 4.0.0 to 6.0.1/6.1.0, this old query suddenly got our indexing stuck:

<delete><query>lastdate_a:{* TO 20160620} AND lastdate_p:{* TO 20160620} AND country:9</query></delete>

with this error logged:

2016-06-20 02:20:36.429 ERROR (commitScheduler-15-thread-1) [   x:mycore] o.a.s.u.CommitTracker auto commit error...:java.lang.NullPointerException
        at org.apache.solr.query.SolrRangeQuery.createDocSet(SolrRangeQuery.java:156)
        at org.apache.solr.query.SolrRangeQuery.access$200(SolrRangeQuery.java:57)
        at org.apache.solr.query.SolrRangeQuery$ConstWeight.getSegState(SolrRangeQuery.java:412)
        at org.apache.solr.query.SolrRangeQuery$ConstWeight.scorer(SolrRangeQuery.java:484)
        at org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight.scorer(LRUQueryCache.java:617)
        at org.apache.lucene.search.BooleanWeight.scorer(BooleanWeight.java:389)
        at org.apache.solr.update.DeleteByQueryWrapper$1.scorer(DeleteByQueryWrapper.java:89)
        at org.apache.lucene.index.BufferedUpdatesStream.applyQueryDeletes(BufferedUpdatesStream.java:694)
        at org.apache.lucene.index.BufferedUpdatesStream.applyDeletesAndUpdates(BufferedUpdatesStream.java:262)
        at org.apache.lucene.index.IndexWriter.applyAllDeletesAndUpdates(IndexWriter.java:3187)
        at org.apache.lucene.index.IndexWriter.maybeApplyDeletes(IndexWriter.java:3173)
        at org.apache.lucene.index.IndexWriter.prepareCommitInternal(IndexWriter.java:2825)
        at org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:2989)
        at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:2956)
        at org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:619)
        at org.apache.solr.update.CommitTracker.run(CommitTracker.java:217)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

The types were:

  <fieldType name="string" class="solr.StrField" sortMissingLast="true" omitNorms="true"/>
  <field name="lastdate_a" type="string" indexed="true" stored="false" />
  <field name="lastdate_p" type="string" indexed="true" stored="false" />
  <field name="country" type="string" indexed="true" stored="true" multiValued="true" />

but changing the date fields into "integer" seems to avoid the problem:

  <fieldType name="integer" class="solr.TrieIntField" omitNorms="true"/>

Issue Links

• is broken by: SOLR-8037 speed up term range queries, use filter cache for embedded ranges