Daniel: It would be great if you would go ahead and edit the Wiki, all you have to do is create a signon. Having just gone through the pain of figuring this out, you're best positioned to know how to warn others!
Best Erick On Thu, Feb 14, 2013 at 4:56 AM, Daniel Rijkhof <daniel.rijk...@gmail.com>wrote: > James, > > I'm not completely sure, and i have not tested the following: > > <entityname>.last_index_time might also not be accessible... > > Daniel > > On Thu, Feb 14, 2013 at 12:47 AM, Daniel Rijkhof > <daniel.rijk...@gmail.com>wrote: > > > James, > > > > I debugged it until I found where things go 'wrong'. > > > > Apparently the current implementation VariableResolver does not allow the > > use of a period '.' in any variable/property key you want to use... It's > > reserved for namespaces. > > Personally I would really love to use a period in my variable/property > key > > names, and see no reason why this should be an issue... > > > > So, using for example > > solr.dataimport.jdbcDriver=org.h2.Driver > > will not work > > > > using just: > > jdbcDriver=org.h2.Driver > > > > works fine... > > > > So i will rename all my properties... but took me hours to find out why > > something that used to work stopped working... > > > > I have never had problems of using periods in any properties > > file... apparently Solr is the only project that doesn't allow the use of > > periods... > > > > Even if this would be documented in a way that persons can find this > > documentation, i guess it would be better to just allow periods by > changing > > the implementation of the VariableResolver just a little... > > > > 00.43 now... off to bed. > > > > Let me know what you think, > > Daniel > > > > > > > > > > On Wed, Feb 13, 2013 at 6:45 PM, Dyer, James < > james.d...@ingramcontent.com > > > wrote: > > > >> The code that resolves variables in DIH was refactored extensively in > >> 4.1.0. So if you've got a case where it does not resolve the variables > >> properly, please give the details. We can open a JIRA issue and get > this > >> fixed. > >> > >> James Dyer > >> Ingram Content Group > >> (615) 213-4311 > >> > >> -----Original Message----- > >> From: Daniel Rijkhof [mailto:daniel.rijk...@gmail.com] > >> Sent: Wednesday, February 13, 2013 11:09 AM > >> To: solr-user@lucene.apache.org > >> Subject: Re: Solr 4.1.0 not using solrcore.properties ? > >> > >> I am looking at the source code of 4.1.0 and I cannot find any prove > that > >> solr 4.1.0's DIH would actually use any properties from the > >> solrcore.properties file. > >> > >> I do however found that Solr does load my solrcore.properties file... > >> > >> It's strange that this would have been changed, > >> > >> Does anybody have prove it still can use properties defined in > >> solrcore.properties within the DIH configuration? > >> > >> In that case, please reply... > >> Daniel > >> > >> Daniel Rijkhof > >> 06 12 14 12 17 > >> > >> > >> On Wed, Feb 13, 2013 at 4:22 PM, Daniel Rijkhof < > daniel.rijk...@gmail.com > >> >wrote: > >> > >> > I have the following problem: > >> > > >> > I'm upgrading from a nightly build 4.0.* to 4.1.0. > >> > > >> > My dataimport is configured with ${variables} which always worked > fine, > >> > untill this upgrade. > >> > > >> > My solrcore.properties file seems to be ignored. > >> > > >> > Solr.xml: > >> > <?xml version="1.0" encoding="UTF-8" ?> > >> > > >> > <solr sharedLib="lib" persistent="true"> > >> > <cores adminPath="/admin/cores" host="${host:}" > >> > hostPort="${jetty.port:}"> > >> > <core default="true" name="hfselectdata" > >> instanceDir="hfselectdata"/> > >> > </cores> > >> > </solr> > >> > > >> > and in <solrhome>/hfselectdata/conf/ is the file solrcore.properties. > >> > > >> > Anybody any suggestions? > >> > > >> > Greatly appreciated > >> > Daniel > >> > > >> > > >> > >> > > >
