[
https://issues.apache.org/jira/browse/SOLR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621570#action_12621570
]
Henri Biestro commented on SOLR-689:
------------------------------------
HossMan; I understand, my question was just syntactical.
The patch today does accomodate properties created at the solr (aka multicore)
& core levels (which allows a core to override "global" defaults) .
I just wanted to know if there were preferences regarding "grouping" them under
a "properties" tag or not. (Much like having <cores> or not to group cores) so
I could prepare a new version of the solr-646 patch (and add a persist test
including properties).
> 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, 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.
