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 ry...@apache.org on 2007/04/28 19:47:35 UTC

svn commit: r533401 - in /lucene/solr/trunk: CHANGES.txt example/solr/conf/solrconfig.xml

Author: ryan
Date: Sat Apr 28 10:47:35 2007
New Revision: 533401

URL: http://svn.apache.org/viewvc?view=rev&rev=533401
Log:
mapping /update to XmlUpdateRequestHandler in the example solrconfig.xml

Modified:
    lucene/solr/trunk/CHANGES.txt
    lucene/solr/trunk/example/solr/conf/solrconfig.xml

Modified: lucene/solr/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/solr/trunk/CHANGES.txt?view=diff&rev=533401&r1=533400&r2=533401
==============================================================================
--- lucene/solr/trunk/CHANGES.txt (original)
+++ lucene/solr/trunk/CHANGES.txt Sat Apr 28 10:47:35 2007
@@ -184,6 +184,13 @@
     <abortOnConfigurationError>false</abortOnConfigurationError>
     in solrconfig.xml (ryan)
 
+ 9. The example solrconfig.xml maps /update to XmlUpdateRequestHandler using 
+    the new request dispatcher (SOLR-104).  This requires posted content to 
+    have a valid contentType: curl -H 'Content-type:text/xml; charset=utf-8' 
+    The response format matches that of /select and returns standard error 
+    codes.  To enable solr1.1 style /update, do not map "/update" to any 
+    handler in solrconfig.xml (ryan)
+
 Optimizations 
  1. SOLR-114: HashDocSet specific implementations of union() and andNot()
     for a 20x performance improvement for those set operations, and a new

Modified: lucene/solr/trunk/example/solr/conf/solrconfig.xml
URL: http://svn.apache.org/viewvc/lucene/solr/trunk/example/solr/conf/solrconfig.xml?view=diff&rev=533401&r1=533400&r2=533401
==============================================================================
--- lucene/solr/trunk/example/solr/conf/solrconfig.xml (original)
+++ lucene/solr/trunk/example/solr/conf/solrconfig.xml Sat Apr 28 10:47:35 2007
@@ -378,26 +378,19 @@
    </requestHandler>
 
   
-  <!-- Standard update plugin.  If we put this on /update, it will get all the new goodness  -->
-  <requestHandler name="/update/xml" class="solr.XmlUpdateRequestHandler" >
-    <!--
-    <lst name="defaults">
-     <str name="name">value</str>
-    </lst>
+  <!-- Update request handler.  
+  
+       Note: Since solr1.1 requestHandlers requires a valid content type header if posted in 
+       the body. For example, curl now requires: -H 'Content-type:text/xml; charset=utf-8'
+       The response format differs from solr1.1 formatting and returns a standard error code.
+       
+       To enable solr1.1 behavior, remove the /update handler or change its path
     -->
-  </requestHandler>
+  <requestHandler name="/update" class="solr.XmlUpdateRequestHandler" />
 
-  <requestHandler name="/debug/dump" class="solr.DumpRequestHandler" >
-    <lst name="defaults">
-     <str name="echoParams">explicit</str> <!-- for all params (including the default etc) 'all' -->
-     <str name="echoHandler">true</str>
-    </lst>
-  </requestHandler>
-  
-  
   <!-- CSV update handler, loaded on demand -->
-  <requestHandler name="/update/csv" class="solr.CSVRequestHandler" startup="lazy">
-  </requestHandler>
+  <requestHandler name="/update/csv" class="solr.CSVRequestHandler" startup="lazy" />
+
 
   <!-- Admin Handlers.  TODO? There could be a single handler that loads them all... -->
   <requestHandler name="/admin/luke"       class="org.apache.solr.handler.admin.LukeRequestHandler" />
@@ -406,6 +399,13 @@
   <requestHandler name="/admin/threads"    class="org.apache.solr.handler.admin.ThreadDumpHandler" />
   <requestHandler name="/admin/properties" class="org.apache.solr.handler.admin.PropertiesRequestHandler" />
   
+  <!-- Echo the request contents back to the client -->
+  <requestHandler name="/debug/dump" class="solr.DumpRequestHandler" >
+    <lst name="defaults">
+     <str name="echoParams">explicit</str> <!-- for all params (including the default etc) use: 'all' -->
+     <str name="echoHandler">true</str>
+    </lst>
+  </requestHandler>
   
   <!-- queryResponseWriter plugins... query responses will be written using the
     writer specified by the 'wt' request parameter matching the name of a registered