If you update to a specific core, I suspect you're getting the doc indexed on two shards which leads to duplicate documents being returned. So it depends on which core happens to answer the request... Fundamentally, all versions of a document must go to the same shard in order for the new version to replace the old version. If you've put the document specifically on a single node, you've bypassed the automatic routing that would insure this...
I think the Admin UI kind of side-steps the usual routing process, but I'm not entirely sure. Best, Erick On Fri, Jun 20, 2014 at 12:47 AM, yann <yannick.lallem...@gmail.com> wrote: > I have the following problem with Solr 4.5.1, with a cloud install with 4 > shards, no replication, using the built-in zookeeper on one Solr: > > I have updated a document via the Solr console (select a core, then select > "Documents"). I used the CSV format to upload the document, including the > document ID. > > When I query the document id from the Solr console (simple query: > id:"the-id-of-the-doc-I-updated"), I alternatively obtain the old document > (with the values before update, and a given _version_ number), or the new > document (with the values after update, and a different _version_). > > No log messages in the Solr console about updating the document or anything. > > Any idea what might be going on, and how to fix that problem? > > Thanks in advance, > > Yann > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-alternates-returning-different-versions-of-the-same-document-tp4143006.html > Sent from the Solr - User mailing list archive at Nabble.com.
