[
https://issues.apache.org/jira/browse/SOLR-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1335:
-----------------------------
Description:
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 or 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
# main master
# slaves of main master
# repeater
# slaves of repeater
It would be nice if I can distribute four properties file so that our ops can
drop the right one and start Solr.
I propose a properties file in the instancedir as solrcore.properties . If
present would be loaded and added as core specific properties.
was:
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 or 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 of
replication
# main master
# slaves of main master
# repeater
#slaves of repeater
It would be nice if I can distribute four properties file so that our ops can
drop the right one and start Solr
I propose a properties file in the instancedir as solrcore.properties . If
present would be loaded and added as core specific properties.
> 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
>
> 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 or 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
> # main master
> # slaves of main master
> # repeater
> # slaves of repeater
> It would be nice if I can distribute four properties file so that our ops can
> drop the right one and start 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.
