[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563346#action_12563346
]
Henri Biestro commented on SOLR-350:
------------------------------------
Regarding introducing variables, this is tempting but this looks like a rather
important feature for a rather limited need. Plus it could be argued that it
increases the element of surprise or at least the potential for side effects.
If a solrconfig/schema refers to a variable that can be superseded in a
multicore.xml, the behavior of a core is explictly dependant on whether it is
loaded in a multicore configuration of not. I agree that being explicit rather
than implicit is better but this does modify behavior even deeper nevertheless.
The door that variable introduction would open seems much wider than the
functional hole is; the original "breach" was needed for the shared class
loader, a common dataDir root is adressing the good practise to segregate data
from configuration. We could introduce a configDir/schemaDir at multicore level
to adress sharing config/schema sharing - although using multiple cores is
usually related to different config/schema so reusing/sharing them does not
look like a must-have feature.
The multicore dataDir attributes is a default directory/roots that can be
overriden by core definitions, the current convention is really limited in its
effects to what's needed. Variables and the huge functional potential of a
whole environment defined within Solr seem way beyond the current use-cases; if
we follow the precedent of "alias vs swap", we should retain the idea but wait
till more needs emerge before implementing it, shouldn't we?
> Manage Multiple SolrCores
> -------------------------
>
> Key: SOLR-350
> URL: https://issues.apache.org/jira/browse/SOLR-350
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Ryan McKinley
> Attachments: SOLR-350-MultiCore.patch, SOLR-350-MultiCore.patch,
> SOLR-350-MultiCore.patch, SOLR-350-Naming.patch, SOLR-350-Naming.patch,
> solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch,
> solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch
>
>
> In SOLR-215, we enabled support for more then one SolrCore - but there is no
> way to use them yet.
> We need to make some interface to manage, register, modify avaliable SolrCores
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
