lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1335) load core properties from a properties file
Date Wed, 19 Aug 2009 05:17:14 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744882#action_12744882
] 

Noble Paul commented on SOLR-1335:
----------------------------------

bq.I also contest your claim that they are alwasy hardcoded for single cores ... we've been
making definite progress down a path of encouraging people to use solr.xml even for single
core setups, as you say..

Are we going to do thiat in 1.4 i.e solr.xml for single cores? But this properties file is
a critical feature for our ops to deploy solr with replication feature. (The master server
is only known at deploy time). currently we are shipping four different solrconfig.xml files

I am not really worried about the specifics of how we implement this. My requirements are
pretty simple
* A core should be able to load properties from a properties file (any file name, any loaction
is OK)
* There should be one sensible default for that file name and location , just the way we have
for schema and solrconfig

What is your preference of doing this?








> 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.


Mime
View raw message