Thanks for getting back. Something like that crossed my mind but I checked the values on the way into SolrJ SolrInputDocument match the values printed in the Admin Query interface and they both match the expected value in the error message exactly.
Besides the difference is only in the last few bits ... Error executing update: version conflict for 553d0f5d320c4321b13f4312ff907218 expected=1498643112821522400 actual=1498643112821522432 Note, all my _version_ values have zeroes in the last two digits. But, again, there is agreement between the Admin UI and every stage of my client (from query in my REST service, to REST client in browser, back to update in my REST service). -----Original Message----- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Thursday, April 16, 2015 5:04 PM To: solr-user@lucene.apache.org Subject: Re: Spurious _version_ conflict? : I notice that the expected value in the error message matches both what : I pass in and the index contents. But the actual value in the error : message is different only in the last (low order) two digits. : Consistently. what does your client code look like? Are you sure you aren't being bit by a JSON parsing library that can't handle long values and winds up truncating them? https://issues.apache.org/jira/browse/SOLR-6364 -Hoss http://www.lucidworks.com/ ************************************************************************* This e-mail may contain confidential or privileged information. If you are not the intended recipient, please notify the sender immediately and then delete it. TIAA-CREF *************************************************************************
