Ok I think I know where the problem is
@Deprecated
169 public SolrIndexWriter(String name, String path,
DirectoryFactory dirFactory, boolean create, IndexSchema schema,
SolrIndexConfig config) throws IOException {
170 super(getDirectory(path, dirFactory, null),
config.luceneAutoCommit, schema.getAnalyzer(), create);
171 init(name, schema, config);
172 }
It's the constructor used by SolrCore in r772051
As you can see, the getDirectory method take a null param instead of
config, resulting a lockType parameter not setted
But in the current trunk, its another constructor thats used so
everything is fine (the SolrConfig instance is in the parameter instead
of null)
Just keeping you updated :)
Thanks for your help
PS : should I fill some kind of bug report even if everything is ok now
? (I'm asking because I didn't see anything related to this problem in
JIRA, so maybe if you want to keep a trace...)
Mani EZZAT wrote:
Should I fill a bug ?
Mani EZZAT wrote:
I tired using the default solrconfig and schema (from the example in 1.3
release) and I still get the same warnings
When I look at the log, the solrconfig seems correcly loaded, but
something is strange :
newSearcher warming query from solrconfig.xml}]}
2010-03-04 10:35:32,545 DEBUG [Config] solrconfig.xml missing optional
mainIndex/deletionPolicy/@class
2010-03-04 10:35:32,556 DEBUG [Config] solrconfig.xml
mainIndex/unlockOnStartup=false
2010-03-04 10:35:32,563 WARN [SolrCore] [core] Solr index directory
'./solr/data/index' doesn't exist. Creating new index...
2010-03-04 10:35:32,589 WARN [SolrIndexWriter] No lockType configured
for ./solr/data/index/ assuming 'simple'
Here I can see solr checking the properties in the Config (or maybe
SolrConfig, not sure about the class) and the lockType property isn't
here... and here comes the warning..
I'm not sure what it means. The information is lost somwhere maybe, but
everything seems fine to me when I look the source code
Also, It happens for the first core I create (and every cores after), so
I don't think its related to the fact that I create dynamically several
cores. Even If i create only 1 core, I'll get the warning since I get it
for the first one anyway
Mani EZZAT wrote:
I don't know, I didn't try because I have the need to create a different
core each time.
I'll do some tests with the default config and will report back to all
of you
Thank you for your time
Tom Hill. wrote:
Hi Mani,
Mani EZZAT wrote:
I'm dynamically creating cores with a new index, using the same schema
and solrconfig.xml
Does the problem occur if you use the same configuration in a single, static
core?
Tom
