solr updates are really a delete followed by a re-index. The old terms are left in the index, but the associated document is marked as deleted. Schema browser, for instance, will happily report frequencies > 1 for <uniqueKey>s when a document has been updated.
You can ignore this if you query on the schemaId in question and get only back one document, it's expected behavior. Also, if this is indeed what you're seeing, doing an optimize (forceMerge in the new parlance) should take all the frequencies back to 1. Best Erick On Thu, Jul 5, 2012 at 9:09 AM, Savvas Andreas Moysidis <savvas.andreas.moysi...@gmail.com> wrote: > hmm, based on the schema I don't see how you would be able to commit > the same "schemaid" twice? > maybe you want to investigate how you post a document to solr (do you > do a commit after the post etc) or the merge strategy that is being > applied. > > Just to exclude any possibilities, is is possible that at some point > the "schemaid" field wasn't defined as "string" and then changed to > "string" without re-indexing? > > On 5 July 2012 12:09, Sohail Aboobaker <sabooba...@gmail.com> wrote: >> <fields> >> <field name="schemaid" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="itemmasterid" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="itemtitle" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="manufacturerId" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="language" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="make" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="model" type="string" indexed="true" stored="true" >> required="true"/> >> <field name="msrp" type="double" indexed="true" stored="true" >> required="true"/> >> <field name="level1Categories" type="string" indexed="true" stored="true" >> required="true" multiValued="true"/><field name="level2Categories" >> type="string" indexed="true" stored="true" required="false" >> multiValued="true"/><field name="level3Categories" type="string" >> indexed="true" stored="true" required="false" multiValued="true"/><field >> name="level4Categories" type="string" indexed="true" stored="true" >> required="false" multiValued="true"/> >> </fields> >> <uniqueKey>schemaid</uniqueKey> >> >> Above is the main schema. Let me know if you need more information.