[SOLR-3432] deleteByQuery silently ignored if updateLog is enabled, but {{_version_}} field does not exist in schema

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.0-ALPHA, 4.0-BETA
• Fix Version/s: 4.0, 6.0

Environment

Tomcat 7

• Assignee: Chris M. Hostetter
• Reporter: David Boychuck
• Created: 03/May/12 00:32
• Updated: 09/May/16 18:56
• Resolved: 21/Aug/12 19:50

Description

deleteByQuery is silently ignored if there the updateLog is configurd in solrconfig.xml, but there is no _version_ field in the schema.xml (ie: if someone copies the example configs, and then prunes down the schema to remove fields they don't think they need/want)

To reproduce:

• comment out _version_ in example schema
• java -jar start.jar
• java -Ddata=args -jar post.jar '<add><doc><field name="id">HOSS</field></doc></add>'
• java -Ddata=args -jar post.jar '<delete><query>id:HOSS</query></delete>'
  • or: java -Ddata=args -jar post.jar '<delete><query>*:*</query></delete>'

Note in the logs that SolrCore logs the deleteByQuery, but there is no log of it executing...

May 3, 2012 4:36:24 PM org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: [collection1] webapp=/solr path=/update params={} {deleteByQuery=*:*} 0 41

Workarround: add this ield to your schema.xml...

   <field name="_version_" type="long" indexed="true" stored="true"/>

Issue Links

• is related to: SOLR-3347 deleteByQuery failing with SolrCloud without _version_ in schema.xml
• is superceded by: SOLR-3746 updateLog should fail to init if there is no _version_ field in schema.xml