[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553983
]
Ryan McKinley commented on SOLR-350:
------------------------------------
> RequestHandlers do not today know the path that requested them;
aaah -- so if we need it later, we could add aliasing then?
> is imho not complex and useful to many (using svn/cvs/webdav to store
> config/schema)
How does aliasing change this. What can you do that you could not do without
it? I store my config/schema in svn and don't have any problems.
> Anyway, the 'aliases' idea is definitely not something you did find useful
> enough from the beginning
If I understood what you gain, I could be convinced. Right now I just see it
as the need to manage and maintain multiple names+one immutable name without
any reason.
Perhaps we can move forward without aliasing, and add it later if we find (and
implement) a solid use case for it.
> 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.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.
