May be a bit late and not strictly about the Multicore "default" discussion but trying to aggregate the ideas; What about an "alias/unalias" feature that would allow managing multiple aliases (at least one) for each core? In the 'multiple index versions' scenario where someone would like to reindex the whole collection because some structural changes needed in the index (analysis chain update for instance), this would allow clean swapping. Say 'articles,3' is my current index & collection with an alias of 'articles' so every client accesses it through 'http://host:port/solr/articles/'. I can create a new core named 'articles,4' with my new index definition (index4), reindex the whole collection and then override the alias for 'articles' when that core is ready. This does not preclude using the multicore feature to other ends (multiple un-related indexes in the same webapp - that could still benefit from the reindexing scenario btw). Not sure if we really need multiple aliases capability; one usage is to allow development, staging/QA & production profiles using the same URLs that would be re-aliased on need so one can develop high level regression tests (ensuring some typical query do get the proper results; dev aliases the core as stage for QA to be performed, QA aliases that core as production when checked). Is this something we could try or are there obvious issues with it?
-- View this message in context: http://www.nabble.com/purpose-of-MultiCore-%22default%22---tp14268755p14373961.html Sent from the Solr - Dev mailing list archive at Nabble.com.
