Have other people tried migrating an index that was created without
block (parent/child) indexing to one that *does* have it? Did you find
that you got duplicate documents - ie multiple documents with the same
uniqueField value? That's what I found, and I don't see how that's
possible.
What I *think* happened was:
Before:
I had various documents in the database, the unique key field was all
set up correctly, when I reindexed, documents would overwrite the
existing document (delete, then update, I guess).
I changed my indexer (this is using a customized version of haystack) to
submit nested document updates instead, so now some of the formerly
"standalone" documents became child documents, and others, parents.
After reindexing:
I had double copies of all the documents; two documents with the same
(uniqueField) id. If I re-indexed again, the parent/child copies would
be overwritten, but a second "standalone" copy seemed to persist (the
_version_ was unchanged). Is the uniqueId field not being applied to
child documents somehow?
Pragmatically speaking it seems I just need to wipe the index and start
over, but I wonder if that is expected?
-Mike
