> On May 15, 2019, at 10:53 AM, Erick Erickson <erickerick...@gmail.com> wrote:
>
> Or something unexpected like there being no <uniqueKey> defined in the schema
> somehow.
Meant to say that somehow the schemas used during your process weren’t what you
thought they were and “somehow” didn’t have a <uniqueKey> defined.
That would require the same doc to be indexed twice of course.
And this also assumes that your process does something like use
EmbeddedSolrServer to index docs. If it uses Lucene directly, then your process
is responsible for handling duplicate <uniqueKeys> properly at the Lucene level.
Best,
Erick
