You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2011/07/26 02:17:15 UTC

[Solr Wiki] Update of "UpdateXmlMessages" by HossMan

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "UpdateXmlMessages" page has been changed by HossMan:
http://wiki.apache.org/solr/UpdateXmlMessages?action=diff&rev1=30&rev2=31

Comment:
"update" refers to the index, you "replace" documents

  = XML Messages for Updating a Solr Index =
  
- Solr accepts POSTed XML messages that Add/Update, Commit, Delete, and Delete by query, using the url '''/update''' (there is also a [[UpdateCSV|CSV]] interface).  Here is the XML syntax that Solr expects to see: 
+ Solr accepts POSTed XML messages that Add/Replace, Commit, Delete, and Delete by query, using the url '''/update''' (there is also a [[UpdateCSV|CSV]] interface).  Here is the XML syntax that Solr expects to see: 
  
  <<TableOfContents>>
  
@@ -10, +10 @@

  
  (Not to be confused with [[SchemaXml|schema.xml]].) 
  
- === add/update ===
+ === add/replace documents ===
  
  Example:
  
@@ -108, +108 @@

   
  The rollback command rollbacks all add/deletes made to the index since the last commit. It neither calls any event listeners nor creates a new searcher.
  
- === "delete" by ID and by Query ===
+ === "delete" documents by ID and by Query ===
  
  Delete by id deletes the document with the specified ID. (ID here means the value of the uniqueKey field declared in the schema (in these examples, employeeId).
  
@@ -154, +154 @@

  
  Until a commit has been issued, you will not see any of the data in searches either on the master or the slave. After a commit has been issued, you will see the results on the master, then after a snapshot has been pulled by the slave, you will see it there also.
  
- === Updating a Data Record via GET ===
+ === Updating via GET ===
  
  Short update requests can also be sent using a GET request (needs to be url-encoded) like: