I would love to see this too. Most of our data comes from a relational database, but there are some files on the file system related to our products that may need to be indexed. The files have different change control / life cycle, so I can't be sure that our application will know when this data changes, so a recurring background re-index job would be helpful. Having to go to the database to get 99% of the data (which didn't change anyway) to send along with the 1% from the file system is a big limitation.
This also prevents the use of DIH. Brandon Ramirez | Office: 585.214.5413 | Fax: 585.295.4848 Software Engineer II | Element K | www.elementk.com -----Original Message----- From: mlevy [mailto:ml...@ushmm.org] Sent: Friday, October 28, 2011 2:21 PM To: solr-user@lucene.apache.org Subject: Re: Partial updates? An ability to update would be extremely useful for us. Different parts of records sometimes come from different databases, and being able to update after creation of the Solr index would be extremely useful. I've made some processes that reads a record and adds a new field to it. The most awkward thing is when there's been a CopyField, when the record is read and re-saved, the copied field causes CopyField to be invoked again. -- View this message in context: http://lucene.472066.n3.nabble.com/Partial-updates-tp502570p3461740.html Sent from the Solr - User mailing list archive at Nabble.com.
