[
https://issues.apache.org/jira/browse/SOLR-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745680#action_12745680
]
Lance Norskog commented on SOLR-1335:
-------------------------------------
About use cases for this feature:
I would like to use this along with my strange baby,
[SOLR-1354|http://issues.apache.org/jira/browse/SOLR-1354]. It would allow me
to push all parameters for an RSS/ATOM feed into a separate configuration file.
This way, to add an rss feed to a Solr instance requires editing a properties
file and nothing else. (The larger goal is here to make it as easy as possible
to make solr useful out of the box.)
Another place where properties files would be very useful is in DIH scripts.
When we want to load multiple shards from the same data source, we need
different code for each shard. It would be great to have one master DIH file
and a different properties file for each shard. Each properties file has a
unique value to define the records for that shard.
> load core properties from a properties file
> -------------------------------------------
>
> Key: SOLR-1335
> URL: https://issues.apache.org/jira/browse/SOLR-1335
> Project: Solr
> Issue Type: New Feature
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 1.4
>
> Attachments: SOLR-1335.patch, SOLR-1335.patch, SOLR-1335.patch
>
>
> There are few ways of loading properties in runtime,
> # using env property using in the command line
> # if you use a multicore drop it in the solr.xml
> if not , the only way is to keep separate solrconfig.xml for each instance.
> #1 is error prone if the user fails to start with the correct system
> property.
> In our case we have four different configurations for the same deployment .
> And we have to disable replication of solrconfig.xml.
> It would be nice if I can distribute four properties file so that our ops can
> drop the right one and start Solr. Or it is possible for the operations to
> edit a properties file but it is risky to edit solrconfig.xml if he does not
> understand solr
> I propose a properties file in the instancedir as solrcore.properties . If
> present would be loaded and added as core specific properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
