solr multivalued field update | DIKSHANT SHAHI
One of the promising features of Solr 4.0 is atomic updates. With the previous releases of Solr, to update a document, you are supposed to send all the fields, even those that have not changed. If you provide only the fields that has changed, the values of other fields will be lost. What does it behave so? It's because Lucene deletes the document and then adds it.
There are many a times, you form Lucene index by reading data from different sources or from different tables in DB. Forming a complete Solr document is a costly operation in many a case, say you are forming a Solr document from different graph DBs. Solr 4.0 sets you free! Just add the field (along with few additional parameters) that is to be updated along with the unique field and you are done. Internally Solr queries the document based on uniqueId, modifies it and adds it back to the index. But it sets you free from doing the same in your client application.
Read full article from solr multivalued field update | DIKSHANT SHAHI
No comments:
Post a Comment