Just do a query on one of the keys that appears to be duplicated and see if
the "duplicates" are also returned.
Also, look at all of the field values for the documents with "duplicated"
keys - are they identical as well, or are there differences in specific
field values. That might highlight when the duplication of keys occurred.
-- Jack Krupansky
-----Original Message-----
From: Robert Krüger
Sent: Wednesday, October 24, 2012 3:25 AM
To: solr-user@lucene.apache.org
Subject: Re: uniqueKey not enforced
On Tue, Oct 23, 2012 at 2:37 PM, Erick Erickson <erickerick...@gmail.com>
wrote:
From left field:
Try looking at your admin/schema browser page for the ID in question.
That actually
gets stuff out of your index (the actual indexed terms). See if you
have two values
I'm running embedded, so I don't have that. However I have a simple UI
for performing queries and the duplicate records are displayed issuing
a "*:*" query.
for that ID. In which case you _might_ have spaces before or after the
value
somehow. I notice your comment says something about "computed", so...
Since
String types are totally unanalyzed, spaces would count.
No, the way the id is computed can not lead to leading or trailing
whitespace.
you can also use the TermsComponent to see what's there, see:
http://wiki.apache.org/solr/TermsComponent
I'll take a look.
Best
Erick
Thanks,
Robert
