[
https://issues.apache.org/jira/browse/SOLR-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris F updated SOLR-5247:
--------------------------
Priority: Trivial (was: Critical)
Description:
This part has been solved. See comments
When using old-style solr.xml I can define custom properties per core like so:
{code:xml}
<cores adminPath="/admin/cores" defaultCoreName="core1">
<core name="core1" instanceDir="core1" config="solrconfig.xml"
schema="schema.xml">
<property name="foo" value="bar" />
</core>
</cores>
{code}
I can then use the property "foo" in schema.xml or solrconfig.xml like this:
{code:xml}
<str name="foo">${foo}</str>
{code}
After switching to the new-style solr.xml with separate core.properties files
per core this does not work anymore.
I guess the corresponding core.properties file should look like this:
{code}
config=solrconfig.xml
name=core1
schema=schema.xml
foo=bar
{code}
(I also tried property.foo=bar)
With that, I get the following error when reloading the core:
{code}
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: No
system property or default value specified for foo value:${foo}
{code}
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:
{code}
http://localhost:8080/solr/admin/cores?action=CREATE&name=core2&instanceDir=core2&config=solrconfig.xml&schema=schema.xml&property.foo=bar&persist=true
{code}
the property "foo" will not appear in core.properties. However, I can use it in
schema.xml. But only until restarting the servlet container. After that, the
property is lost.
Possibly related to [SOLR-5208|https://issues.apache.org/jira/browse/SOLR-5208]?
was:
This part has been solved. See comments
When using old-style solr.xml I can define custom properties per core like so:
{code:xml}
<cores adminPath="/admin/cores" defaultCoreName="core1">
<core name="core1" instanceDir="core1" config="solrconfig.xml"
schema="schema.xml">
<property name="foo" value="bar" />
</core>
</cores>
{code}
I can then use the property "foo" in schema.xml or solrconfig.xml like this:
{code:xml}
<str name="foo">${foo}</str>
{code}
After switching to the new-style solr.xml with separate core.properties files
per core this does not work anymore.
I guess the corresponding core.properties file should look like this:
{code}
config=solrconfig.xml
name=core1
schema=schema.xml
foo=bar
{code}
(I also tried property.foo=bar)
With that, I get the following error when reloading the core:
{code}
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: No
system property or default value specified for foo value:${foo}
{code}
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:
{code}
http://localhost:8080/solr/admin/cores?action=CREATE&name=core2&instanceDir=core2&config=solrconfig.xml&schema=schema.xml&property.foo=bar&persist=true
{code}
the property "foo" will not appear in core.properties file.
Possibly related to [SOLR-5208|https://issues.apache.org/jira/browse/SOLR-5208]?
> Support for custom per core properties missing with new-style solr.xml
> ----------------------------------------------------------------------
>
> Key: SOLR-5247
> URL: https://issues.apache.org/jira/browse/SOLR-5247
> Project: Solr
> Issue Type: Bug
> Components: multicore
> Affects Versions: 4.4
> Reporter: Chris F
> Priority: Trivial
> Labels: 4.4, core.properties, discovery, new-style, property,
> solr.xml
>
> This part has been solved. See comments
> When using old-style solr.xml I can define custom properties per core like so:
> {code:xml}
> <cores adminPath="/admin/cores" defaultCoreName="core1">
> <core name="core1" instanceDir="core1" config="solrconfig.xml"
> schema="schema.xml">
> <property name="foo" value="bar" />
> </core>
> </cores>
> {code}
> I can then use the property "foo" in schema.xml or solrconfig.xml like this:
> {code:xml}
> <str name="foo">${foo}</str>
> {code}
> After switching to the new-style solr.xml with separate core.properties files
> per core this does not work anymore.
> I guess the corresponding core.properties file should look like this:
> {code}
> config=solrconfig.xml
> name=core1
> schema=schema.xml
> foo=bar
> {code}
> (I also tried property.foo=bar)
> With that, I get the following error when reloading the core:
> {code}
> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: No
> system property or default value specified for foo value:${foo}
> {code}
> 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:
> {code}
> http://localhost:8080/solr/admin/cores?action=CREATE&name=core2&instanceDir=core2&config=solrconfig.xml&schema=schema.xml&property.foo=bar&persist=true
> {code}
> the property "foo" will not appear in core.properties. However, I can use it
> in schema.xml. But only until restarting the servlet container. After that,
> the property is lost.
> Possibly related to
> [SOLR-5208|https://issues.apache.org/jira/browse/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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
