Oh I see, thanks for the clarification. Unfortunately this brings me back to same problem I started with: implicit properties aren't available when managing indexes through the REST api. I know there is a patch in the works for this issue but I can't wait for it. Is there any way to share the solrconfig.xml file and create indexes dynamically?
Mark On Mon, Jan 26, 2009 at 9:02 PM, Noble Paul നോബിള് नोब्ळ् < noble.p...@gmail.com> wrote: > The behavior is expected > properties set in solr.xml are not implicitly used anywhere. > you will have to use those variables explicitly in > solrconfig.xml/schema.xml > instead of hardcoding dataDir in solrconfig.xml you can use it as a > variable <dataDir>$$dataDir</dataDir> > > BTW there is an issue (https://issues.apache.org/jira/browse/SOLR-943) > which helps you specify the dataDir in solr.xml > > > On Tue, Jan 27, 2009 at 5:19 AM, Mark Ferguson > <mark.a.fergu...@gmail.com> wrote: > > Hi, > > > > In my solr.xml file, I am trying to set the dataDir property the way it > is > > described in the CoreAdmin page on the wiki: > > > > <core name='p11' instanceDir='./'> > > <property name="dataDir" value="./data/p11" /> > > </core> > > > > However, the property is being completed ignored. It is using whatever I > > have set in the solrconfig.xml file (or ./data, the default value, if I > set > > nothing in that file). Any idea what I am doing wrong? I am trying this > > approach to avoid using ${solr.core.name} in the solrconfig.xml file, > since > > dynamic properties are broken for creating cores via the REST api. > > > > Mark > > > > > > -- > --Noble Paul >
