a full index from scratch? If
so, try rebuilding the index.
People often get the behavior you describe if the 'id' is a 'text' field.
ryan
--
View this message in context:
http://www.nabble.com/SOLR-1.2---Duplicate-Documents---tp13621332p14531206.html
Sent from the Solr - User
On Nov 7, 2007 12:30 PM, realw5 [EMAIL PROTECTED] wrote:
We did have Tomcat crash once (JVM OutOfMem) durning an indexing process,
could that be a possible source of the issue?
Yes.
Deletes are buffered and carried out in a different phase.
-Yonik
Schema.xml
field name=id type=string indexed=true stored=true/
Have you edited schema.xml since building a full index from scratch? If
so, try rebuilding the index.
People often get the behavior you describe if the 'id' is a 'text' field.
ryan
: Hey all, I have a fairly odd case of duplicate documents in our solr index
: (See attached xml sample). THe index is roughtly 35k in documents. The only
How did you index those documents?
Any chance you inadvertently set the allowDups=true attribute when
sending them to Solr (possibly
you edited schema.xml since building a full index from scratch? If
so, try rebuilding the index.
People often get the behavior you describe if the 'id' is a 'text' field.
ryan
--
View this message in context:
http://www.nabble.com/SOLR-1.2---Duplicate-Documents---tf4762687.html
/defaultSearchField
!-- SolrQueryParser configuration: defaultOperator=AND|OR --
solrQueryParser defaultOperator=OR/
--
View this message in context:
http://www.nabble.com/SOLR-1.2---Duplicate-Documents---tf4762687.html#a13621332
Sent from the Solr - User mailing list archive at Nabble.com.