[ https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553809 ]
ryantxu edited comment on SOLR-350 at 12/20/07 2:44 PM: -------------------------------------------------------------- > (be it, filtered queries, query parsers, etc) would open to easy ways to fit > per-user/usage profiles behaviors. > Are you saying there is a big win if you can get stats on: http://host/henri/select vs http://host/ryan/select when 'henri' and 'ryan' are both aliased to 'core1'? Perhaps? but mod_rewrite can do that and much much more (if you really wanted to). With the alias model, how would you reindex a running core and end up with an identical setup at the end? Unless I'm missing something, the new core would need a different name (id), and there would be a brief moment where the main core was not avaliable consider: <core name="core0" alias="main" ... /> and all queries come to solr as: http://host/solr/main/... I would have to run: 1. LOAD core1 using same config as core0 2. send add commands to core1 3. UNALIAS "main" from core0 (now nothing is available at /main) 4. ALIAS "main" to core1 5. UNLOAD core0 (now the persisted configuration is different then when we started but should not be) was (Author: ryantxu): > (be it, filtered queries, query parsers, etc) would open to easy ways to fit > per-user/usage profiles behaviors. > Are you saying there is a big win if you can get stats on: http://host/henri/select vs http://host/ryan/select when 'henri' and 'ryan' are both aliased to 'core1'? Perhaps? but mod_rewrite can do that and much much more (if you really wanted to). With the alias model, how would you reindex a running core and end up with an identical setup at the end? Unless I'm missing something, the new core would need a different name (id), and there would be a brief moment where the main core was not avaliable consider: <core name="core0" alias="main" ... /> and all queries come to solr as: http://host/solr/main/... I would have to run: 1. LOAD core1 using same config as core0 2. send add commands to core1 3. UNALIAS "main" from core0 (now nothing is available at /main) 4. ALIAS "main" to core1 (not the persisted configuration is different then when we started) > 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.