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 JanHoydahl: http://wiki.apache.org/solr/SolrConfigXml?action=diff&rev1=49&rev2=50 Comment: Updating about indexConfig {{{ <dataDir>/var/data/solr</dataDir> }}} - == indexDefaults Section == - /!\ :TODO: /!\ Still need a section explaining indexDefaults - == mainIndex Section == + == indexConfig Section == + <!> [[Solr3.6]] + These settings control low-level behavior of indexing. Please see comments in the example solrconfig.xml for details. + + Note: In versions prior to 3.6, there were two different sections named <indexDefaults> and <mainIndex>, which are now replaced with this one <indexConfig> section. You can still use the old config as is in 3.6 and 4.x, but need to migrate when bumping luceneMatchVersion. Easiest way to migrate is to start with the example <indexConfig> section which has everything commented out, using the defaults, and then customize if necessary. - The values in this section controls the merging of multiple index segments. See the `mergeFactor` Considerations section on the SolrPerformanceFactors doc for more details. - - {{{ - <mainIndex> - <!-- lucene options specific to the main on-disk lucene index --> - <useCompoundFile>false</useCompoundFile> - <mergeFactor>10</mergeFactor> - <maxBufferedDocs>1000</maxBufferedDocs> - <maxMergeDocs>2147483647</maxMergeDocs> - <maxFieldLength>10000</maxFieldLength> - </mainIndex> - }}} - The `maxMergeDocs` parameter tells Lucene to not to allow any segment to contain more docs than the value stipulated, but to create a new segment instead. == Update Handler Section == The Update Handler section mostly relates to low level information about how updates are handled internally (do not confuse with higher level configuration of "Request Handlers" for dealing with updates sent by clients)
