Thanks for letting us know.
Erick
On Tue, Jun 24, 2014 at 5:25 AM, yann wrote:
> Hi Erik,
>
> thanks - if it helps, I eventually fixed the problem by deleting the
> documents by id (via an http request), which apparently deleted all the
> versions everywhere, then re-creating the documents via
Hi Erik,
thanks - if it helps, I eventually fixed the problem by deleting the
documents by id (via an http request), which apparently deleted all the
versions everywhere, then re-creating the documents via the admin interface
(update, csv). This seems to have left only one version of each documen
bq: If I understood you correctly - this means the update section of the admin
should be avoided when using a sharded install, because it doesn't guarantee
a given document ID will be sent to the same shard as the previous version
of the same document?
You've got it, but I want to emphasize th
Hi Erik,
thanks for your answer. I didn't manually assign docs to shards, I indexed
all docs on one server, which then assigned it to shards (based on the
default Solr behaviour, based on the document ID I believe).
If I understood you correctly - this means the update section of the admin
should
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 t
