Let's see the schema file and a sample input document please. Possibly there's something you're overlooking...
And what is your evidence that the document isn't overwritten? Because an update is really a delete, followed by an add. The delete just marks the document as deleted, it doesn't physically remove it from the index, an optimize is required for that to occur. So if you're looking at a low level, the docs may be, in fact, removed from searches, and you're being mislead by the low-level nature of your examination. It's possible anyway. Best Erick On Wed, Mar 30, 2011 at 7:59 AM, Carl-Erik Herheim <carl-erik.herh...@nsd.uib.no> wrote: > Yes, I have. > > Den 30.03.2011 13:41, skrev Markus Jelsma: >> >> Have you defined a uniqueKey in your schema? >> >> http://wiki.apache.org/solr/SchemaXml#The_Unique_Key_Field >> >> >> On Wednesday 30 March 2011 13:16:02 Carl-Erik Herheim wrote: >>> >>> Hi list, >>> I've got a multi-core solr index that is indexed through solrj. The >>> problem is that already existing documents don't get overwritten when >>> they are re-indexed. This means we have to empty the index whenever we >>> want to update it, which isn't really an option. From what I've been >>> reading I was under the impression that documents get overwritten by >>> default, but that doesn't seem to be the case. Is there anything I can >>> do to force overwriting? >>> The way we index it now is (to put it simply): >>> CommonsHttpSolrServer.add(List<SolrInputDocument>) >>> >>> Any help appreciated, thanks! >>> >>> - Carl-Erik > >
