lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Russakovskii (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1335) load core properties from a properties file
Date Thu, 24 Sep 2009 03:17:16 GMT

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

Artem Russakovskii commented on SOLR-1335:
------------------------------------------

Paul, thank you. How funny - I was using nightly build from 8/25/09 and looks like the final
commit was made on 8/26/09. Doh!

So I verified $solr_home/conf/solrcore.properties as working, and it's good enough for us,
but it'd be ideal if this location can be specified in solrconfig.xml, for example to be set
to '$solr_home/..'. However,

a) I'm not sure this is supported right now
b) I think we came to a conclusion in another ticket that there's no value $solr_home that
one can refer to from within solrconfig.xml (http://www.nabble.com/Solr,-JNDI-config,-dataDir,-and-solr-home-problem-td25286277.html
and SOLR-1414), although it looks like you may have fixed it - is it accessible by ${solr.core.instanceDir}
 now?

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