lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris F (JIRA)" <>
Subject [jira] [Created] (SOLR-5247) Support for custom per core properties missing with new-style solr.xml
Date Wed, 18 Sep 2013 11:32:51 GMT
Chris F created SOLR-5247:

             Summary: Support for custom per core properties missing with new-style solr.xml
                 Key: SOLR-5247
             Project: Solr
          Issue Type: Bug
          Components: multicore
    Affects Versions: 4.4
            Reporter: Chris F
            Priority: Critical

When using old-style solr.xml I can define custom properties per core like so:
<cores adminPath="/admin/cores" defaultCoreName="core1">
  <core name="core1" instanceDir="core1" config="solrconfig.xml" schema="schema.xml">
    <property name="foo" value="bar" />
I can then use the property "foo" in schema.xml or solrconfig.xml like this:
<str name="foo">${foo}</str>

After switching to the new-style solr.xml with separate files per core this
does not work anymore.

I guess the corresponding file should look like this:
(I also tried

With that, I get the following error when reloading the core:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: No system property
or default value specified for foo value:${foo}
I can successfully reload the core if I use ${foo:undefined} but the value of "foo" will always
be "undefined" then.

When trying to create a new core with an url like this:
the property "foo" will not appear in file.

Related to [SOLR-5208|]?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message