[
https://issues.apache.org/jira/browse/SOLR-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724805#action_12724805
]
Noble Paul edited comment on SOLR-1198 at 6/26/09 10:50 PM:
------------------------------------------------------------
bq.by containing everything in SolrConfig, you could make a different
SolrConfig ...
amen..
The intent is to be able to load a core using an API. So I should be able to
load my configuration from anywhere say zookeeper, a db etc etc
But this is not very easy to squeeze this into 1.4 . so we can push it to 1.5
until we iron out the details
But what is already done lets me share solrconfig objects and reduce core load
time drastically for our massively multicore search system. ~30000 cores in a
box with ~4000 cores loaded at a given time
was (Author: noble.paul):
bq.by containing everything in SolrConfig, you could make a different
SolrConfig ...
amen..
The intent is to be able to load a core using an API. So I should be able to
load my configuration from anywhere say zookeeper, a db etc etc
> confine all solrconfig.xml parsing to SolrConfig.java
> -----------------------------------------------------
>
> Key: SOLR-1198
> URL: https://issues.apache.org/jira/browse/SOLR-1198
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 1.4
>
> Attachments: SOLR-1198.patch, SOLR-1198.patch, SOLR-1198.patch,
> SOLR-1198.patch, SOLR-1198.patch, SOLR-1198.patch, SOLR-1198.patch
>
>
> Currently , xpath evaluations are spread across Solr code. It would be
> cleaner if if can do it all in one place . All the parsing can be done in
> SolrConfig.java
> another problem with the current design is that we are not able to benefit
> from re-use of solrconfig object across cores.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
