[ 
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553885
 ] 

Ryan McKinley commented on SOLR-350:
------------------------------------

> If we were to use the 'alias' to map behaviors, 

how would an alias map different behaviors?  Alias just offer multiple ways to 
access the *same* core and the same behavior.  RequestHandlers don't know what 
path requested them.

My point about mod_rewrite was referring to the use case you referred to:  
making the log files easier to parse per user.  

Re production and stage, why do you need aliasing for that?  each core has name 
- when 'stage' is ready -- it can swap with 'production'  

> Finally, the 'alias' command as it stands, allows to redefine an alias 
> (without havng to unalias first) so the sequence would be:
> (considering <core name="core,0" alias="main" ... />)
> LOAD core,1  // which could even be aliased as 'stage' at this time
> send adds to core,1 // when done, could run verifications on 'stage'
> ALIAS core,1 main // 'swap' so to speak, overwrites previous 'main' alias
> UNLOAD core,0
> 

so if you serialize at the beginning, you have:
<core name="core,0" alias="main" ... />
at the end you have:
<core name="core,1" alias="main" ... />

if you run that every hour, do you end up with "core,1000" or switch between 
them?  This would require you ask MultiCore, what i the 'id' for the core 
sitting at 'main' before you can operate on it.  Why add this complexity?

> 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.

Reply via email to