[Solr Wiki] Update of "CoreAdmin" by ShalinMangar

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "CoreAdmin" page has been changed by ShalinMangar:
http://wiki.apache.org/solr/CoreAdmin?action=diff&rev1=49&rev2=50

Comment:
Added details on SPLIT action

  
  Merge indexes into a another index.  This is described more fully at MergingSolrIndexes.
  
+ == SPLIT ==
+ 
+ <!> [[Solr4.3]]
+ 
+ Splits an index into two or more indexes. It accepts the following parameters:
+  * "core" - The core whose index is to be split
+  * "path" - The file path to which the pieces of the "core"'s index will be written (multi-valued parameter)
+  * "targetCore" - The target solr core (which must already exist) to which the pieces of the split index will be merged (multi-valued parameter)
+ 
+ Either "path" or "targetCore" must be specified (but not both). At least two values for "path" or "targetCore" must be specified.
+ 
+ Example:
+ 
+  * http://localhost:8983/solr/admin/cores?action=SPLIT&core=core0&targetCore=core1&targetCore=core2
+  * http://localhost:8983/solr/admin/cores?action=SPLIT&core=core0&path=/path/to/index/1&path=/path/to/index/2
+ 
+ This command is used as part of the SPLITSHARD SolrCloud Collection API but it can be used for non-cloud Solr cores as well. When used against a non-cloud core, this action will split the source index into parts containing an equal number of documents.
+ 
  = Known Issues =
  Lucene's BooleanQuery maxClauseCount is a static variable, making it a single value across the entire JVM.  Whichever Solr core initializes last will win the setting of the solrconfig.xml's maxBooleanClauses value.  Workaround, set maxBooleanClauses to the greatest value desired in *all* cores.