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 Apache Wiki <wi...@apache.org> on 2010/10/11 17:33:47 UTC

[Solr Wiki] Update of "CoreAdmin" by DavidSmiley

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 DavidSmiley.
The comment on this change is: Document defaultCoreName.
http://wiki.apache.org/solr/CoreAdmin?action=diff&rev1=28&rev2=29

--------------------------------------------------

  == cores ==
  The `<cores>` tag accepts the following attributes:
    *'''adminPath''' - Relative path to access the !CoreAdminHandler for dynamic core manipulation.  For example, adminPath="/admin/cores" configures access via http://localhost:8983/solr/admin/cores.  If this attribute is not specified, dynamic manipulation is unavailable.
+   ** <!> [[Solr1.4]] '''defaultCoreName''' - The name of a core that will be used for requests that don't specify a core.  If you have one core and want to use the features specified on this page, then this provides a way to keep your URLs the same.
    ** <!> [[Solr1.4]] '''shareSchema''' - The value can be 'true' or 'false'. This ensures that the multiple cores pointing to the same schema.xml will be referring to the same !IndexSchema Object. This makes loading the core faster. Ensure that no core specific property is used in your schema.xml.
    * <!> [[Solr1.4]] '''adminHandler''' - FQN(Fully qualified name) of a class that  inherits from !CoreAdminHandler.  For example, adminHandler="com.myorg.!MyAdminHandler" would configure the custom admin handler (!MyAdminHandler) to handler admin requests ( as opposed to org.apache.solr.handler.admin.!CoreAdminHandler , that is the default admin handler if one is not specified ). To illustrate an use case for the same - suppose if there is a need to get some statistics from different cores in a solr instance - we would proceed as follows. 
     * Define a new action called 'mystat' that could be accessed from the client  as below.