I guess another way to pose the question is- what could cause
<uniqueKey>id</uniqueKey> to no longer be respected?
The last chance I made since I noticed the problem of non-unique docs
was by changing field "title" from "string" to "SplitUpStuff". But I
dont understand how that could affect the uniqueness of a different
field called "id".
<fieldType name="splitUpStuff" class="solr.TextField"
positionIncrementGap="100">
<analyzer type="index">
<filter class="solr.WordDelimiterFilterFactory"
generateWordParts="1" generateNumberParts="0" c
<filter class="solr.StopFilterFactory"
ignoreCase="true"
words="stopwords.txt"
enablePositionIncrements="false"
/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.EnglishPorterFilterFactory"
protected="protwords.txt"/>
<filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
</analyzer>
</fieldType>
In order to make even a guess, we'd have to see your new
field type. Particularly its field definitions and the analysis
chain...
Best
Erick
On Fri, Aug 13, 2010 at 5:16 PM, j <[email protected]> wrote:
> Does fieldType have any effect on the thing that I specify should be
> unique?
>
> uniqueKey has been working for me up until recently. I change the
> field that is unique from type "string" to a fieldType that I have
> defined. Now when I do an update I get a newly created document (so
> that I have duplicates).
>
> Has anyone else had this problem before?
>
