This should not be the case. Any time you add a document with a pre-existing <unkqueKey>, the old document is completely replaced by the new document.
You do have to issue a commit before you'll see the new info though. And if you do not have a <uniqueKey> defined, you'll see two copies of the doc. And sometimes your browser cache will fool you... Best Erick On Tue, Sep 11, 2012 at 8:21 PM, Mani <mehamba...@art.com> wrote: > Eric, > "When you add a doc with the same unique key as an old doc, > the data associated with the first version of the doc is entirely > thrown away and its as though you'd never indexed it at all", I did exactly > the same. The old doc and new doc there is not a change except the Name has > changed. When I query Solr for the document, I do see the Name field with > the correct recent changes. However if I search for for the new name, I do > not get the result. So I removed all the documents entirely and then added > the same new document. It worked. Not sure if this is a bug. > > So whenever I add a new field to an existing search field, the document > needs to be thrown away (not just adding with the same key as its not > working in my case) for the search to take effect. > > Thanks > > > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-search-not-working-after-copying-a-new-field-to-an-existing-Indexed-Field-tp4005993p4007096.html > Sent from the Solr - User mailing list archive at Nabble.com.
