Dear Wiki user,

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

The "SolrConfigXml" page has been changed by DmitryKan:
http://wiki.apache.org/solr/SolrConfigXml?action=diff&rev1=57&rev2=58

Comment:
fixed the shardHandlerFactory xml closing tag

  {{{
    <dataDir>/var/data/solr</dataDir>
  }}}
- 
  <!> NOTE: begining with [[Solr4.0]] attempting to change the {{{<dataDir>}}} 
and then RELOAD the core will not work because it is a 
[[CoreAdmin#LiveReload|Live Reload]].
  
  == codecFactory ==
- 
- <!> [[Solr4.0]]
- Codec factories allow your schema to use custom codecs. For example, if you 
want to define per-field postings formats, you can use the built-in 
SchemaCodecFactory:
+ <!> [[Solr4.0]] Codec factories allow your schema to use custom codecs. For 
example, if you want to define per-field postings formats, you can use the 
built-in SchemaCodecFactory:
+ 
  {{{
    <codecFactory name="CodecFactory" class="solr.SchemaCodecFactory" />
  }}}
- 
  Please note that there are some limitations and core reloading might not work 
as expected when custom codec factories are defined 
([[https://issues.apache.org/jira/browse/SOLR-3610|SOLR-3610]]).  For detailed 
instructions on how to configure SimpleTextCodec, see: 
[[http://wiki.apache.org/solr/SimpleTextCodecExample|SimpleTextCodec Example]]
  
  == indexConfig Section ==
- <!> [[Solr3.6]]
- These settings control low-level behavior of indexing. Please see comments in 
the example solrconfig.xml for details.
+ <!> [[Solr3.6]] These settings control low-level behavior of indexing. Please 
see comments in the example solrconfig.xml for details.
  
  <!> NOTE: begining with [[Solr4.0]] attempting to change Index Writer related 
settings in {{{<indexConfig>}}} and then RELOAD the core will not work because 
it is a [[CoreAdmin#LiveReload|Live Reload]].
  
@@ -61, +57 @@

  
      ...
  }}}
- 
  <!> [[Solr4.0]]
  
  {{{
     ...
-      <autoCommit> 
+      <autoCommit>
-        <maxTime>1000</maxTime> 
+        <maxTime>1000</maxTime>
       </autoCommit>
  
      <!-- SoftAutoCommit
@@ -80, +75 @@

  
           maxTime - Maximum amount of time in ms that is allowed to pass
                     since a document was added before automaticly
-                    triggering a new soft commit. 
+                    triggering a new soft commit.
        -->
  
-      <autoSoftCommit> 
+      <autoSoftCommit>
-        <maxTime>1000</maxTime> 
+        <maxTime>1000</maxTime>
       </autoSoftCommit>
  
      ...
  }}}
- 
- 
  === "Update" Related Event Listeners ===
  Within the Update Handler Section, you can define listeners for particular 
"update" related events: "postCommit" and "postOptimize".  Listeners can be 
used to fire-off any special code; they are typically used to exec snapshooter.
  
@@ -346, +339 @@

    <requestHandler name="standard" class="solr.StandardRequestHandler" />
    <requestHandler name="custom" class="your.package.CustomRequestHandler" />
  }}}
- 
  === Configuration of Shard Handlers for Distributed searches ===
  Inside requestHandlers it is possible to configure and specify the shard 
handler used for distributed search, it is possible to plug in custom shard 
handlers as well as configure the provided solr version.
  
@@ -358, +350 @@

       <shardHandlerFactory class="HttpShardHandlerFactory">
          <int name="socketTimeOut">1000</int>
          <int name="connTimeOut">5000</int>
-       </shardHandler>
+       </shardHandlerFactory>
    </requestHandler>
  }}}
- 
  The parameters that can be specified are as follows:
+ 
   * socketTimeout. default: 0 (use OS default) - The amount of time in ms that 
a socket is allowed to wait for
   * connTimeout. default: 0 (use OS default) - The amount of time in ms that 
is accepted for binding / connection a socket
   * maxConnectionsPerHost. default: 20 - The maximum number of connections 
that is made to each individual shard in a distributed search
@@ -508, +500 @@

  
  This might be useful in cases where there are a number of settings that only 
differ if the server is a master or a slave.  These settings could be factored 
out into two separate files and then included as needed to avoid duplication of 
common portions of solrconfig.xml
  
- The following sample attempts to include solrconfig_master.xml.  If it 
doesn't exist or can't be loaded, then solrconfig_slave.xml will be used 
instead.  If solrconfig_slave.xml can't be loaded an XML parsing exception will 
result.  
+ The following sample attempts to include solrconfig_master.xml.  If it 
doesn't exist or can't be loaded, then solrconfig_slave.xml will be used 
instead.  If solrconfig_slave.xml can't be loaded an XML parsing exception will 
result.
  
  {{{
      <xi:include href="solrconfig_master.xml" 
xmlns:xi="http://www.w3.org/2001/XInclude";>

Reply via email to