[
https://issues.apache.org/jira/browse/SOLR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499919
]
Otis Gospodnetic commented on SOLR-215:
---------------------------------------
Henri - I'm starting to ook at this. I see a lot of space changes in the
patch. Could you please generate a patch that doesn't have all those space
changes?
When you generate a diff file for the patch, these may be handy parameters to
use (I'm assuming you're going work under some kind of UNIX)
-E --ignore-tab-expansion
Ignore changes due to tab expansion.
-b --ignore-space-change
Ignore changes in the amount of white space.
-w --ignore-all-space
Ignore all white space.
-B --ignore-blank-lines
Ignore changes whose lines are all blank.
Thanks!
I just skimmed the patch and didn't see where the name of the index/core gets
passed in the request. Can you please point me to the right place to look?
> Multiple Solr Cores
> -------------------
>
> Key: SOLR-215
> URL: https://issues.apache.org/jira/browse/SOLR-215
> Project: Solr
> Issue Type: Improvement
> Reporter: Henri Biestro
> Priority: Minor
> Attachments: solr-trunk-533775.patch, solr-trunk-538091.patch,
> solr-trunk-src.patch
>
>
> Allow multiple cores in one web-application (or one class-loader):
> This allows to have multiple cores created from different config & schema in
> the same application.
> The side effect is that this also allows different indexes.
> Implementation notes for the patch:
> The patch allows to have multiple 'named' cores in the same application.
> The current single core behavior has been retained - the core named 'null' -
> but code could not be kept 100% compatible. (In particular, Solrconfig.config
> is gone; SolrCore.getCore() is still here though).
> A few classes were only existing as singletons and have thus been refactored.
> The Config class feature-set has been narrowed to class loading relative to
> the installation (lib) directory;
> The SolrConfig class feature-set has evolved towards the 'solr config' part,
> caching frequently accessed parameters;
> The IndexSchema class uses a SolrConfig instance; there are a few parameters
> in the configuration that pertain to indexing that were needed.
> The SolrCore is built from a SolrConfig & an IndexSchema.
> The creation of a core has become:
> //create a configuration
> SolrConfig config = SolrConfig.createConfiguration("solrconfig.xml");
> //create a schema
> IndexSchema schema = new IndexSchema(config, "schema0.xml");
> //create a core from the 2 other.
> SolrCore core = new SolrCore("core0", "/path/to/index", config, schema);
> //Accessing a core:
> SolrCore core = SolrCore.getCore("core0");
> There are few other changes mainly related to passing through constructors
> the SolrCore/SolrConfig used.
> Some background on the 'whys':
> http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10082201
> http://www.nabble.com/Embedding-Solr-vs-Lucene%2C-multiple-Solr-cores--tf3572324.html#a9981355
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
