[
https://issues.apache.org/jira/browse/SOLR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621334#action_12621334
]
Ryan McKinley commented on SOLR-689:
------------------------------------
Since we are already throwing a wrench at anyone who has an existing
multicore.xml file, I think we should go ahead and make the other name changes:
{code:xml}
<multicore adminPath="/admin/multicore" persistent="true" >
<core name="core0" instanceDir="core0" />
<core name="core1" instanceDir="core1" />
</multicore>
{code}
to
{code:xml}
<solr coreAdminHandler="/admin/multicore" persistent="true" >
<core name="core0" instanceDir="core0" />
<core name="core1" instanceDir="core1" />
</solr>
{code}
I agree that internal class refactoring can change later (or sooner), but if we
muck with the external configs, we should do everything at once.
> rename multicore.xml solr.xml
> -----------------------------
>
> Key: SOLR-689
> URL: https://issues.apache.org/jira/browse/SOLR-689
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Fix For: 1.3
>
> Attachments: SOLR-689.patch
>
>
> Per mailing list discussion (see link below) it seems prudent to rename
> multicore.xml to solr.xml prior to the 1.3 release.
> short summary of the main motivations for doing this...
> {noformat}
> 1) The name of the file corresponds with one specific way it can be
> used, but may not be applicable to all usages (namely: you can
> have a multicore.xml file but only use one core)
> 2) The "first" config file checked to determine the application's
> behavior, and what paths will be checked for other config files
> is named after one specific feature of the application.
> {noformat}
> General consensus of the thread so far seems to be that this is a good idea,
> and gives us more options for the future.
> http://www.nabble.com/Rename-multicore.xml---to18877268.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
