config/solr/cores/en/conf/solrconfig.xml in muck-raker-0.1.27 vs config/solr/cores/en/conf/solrconfig.xml in muck-raker-0.1.28
- old
+ new
@@ -240,11 +240,11 @@
handleSelect=true will use consistent error handling for /select and /update
handleSelect=false will use solr1.1 style error formatting
-->
<requestDispatcher handleSelect="true" >
<!--Make sure your system has some authentication before enabling remote streaming! -->
- <requestParsers enableRemoteStreaming="false" multipartUploadLimitInKB="2048" />
+ <requestParsers enableRemoteStreaming="true" multipartUploadLimitInKB="2048" />
</requestDispatcher>
<!-- requestHandler plugins... incoming queries will be dispatched to the
correct handler based on the qt (query type) param matching the
@@ -263,21 +263,28 @@
<str name="version">2.1</str>
-->
</lst>
</requestHandler>
+ <requestHandler name="mlt" class="solr.MoreLikeThisHandler">
+ <lst name="defaults">
+ <str name="mlt.fl">text</str>
+ <int name="mlt.mindf">1</int>
+ </lst>
+ </requestHandler>
+
<!-- Note how you can register the same handler multiple times with
different names (and different init parameters)
-->
<!-- 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 name="/update" class="solr.XmlUpdateRequestHandler" />
-->
+ <requestHandler name="/update" class="solr.XmlUpdateRequestHandler" />
<!-- queryResponseWriter plugins... query responses will be written using the
writer specified by the 'wt' request parameter matching the name of a registered
writer.
The "standard" writer is the default and will be used if 'wt' is not specified