|
|
Issue Type:
|
Code Task
|
Affects Versions:
|
4.1
|
Assignee:
|
Unassigned
|
Components:
|
Solr
|
Created:
|
10/Jun/14 8:26 AM
|
Priority:
|
Minor
|
Reporter:
|
Christian Völker
|
|
During each startup 27 Warnings get logged to catalina.out, due to configuration settings which I believe were made unintentionally. This distracts attention when searching for actual problems. These three files differ slightly, but all exhibit the same two issues: /dspace/solr/oai/conf/solrconfig.xml /dspace/solr/search/conf/solrconfig.xml /dspace/solr/statistics/conf/solrconfig.xml Around line 60-85, there is an example that makes the classloader throw warnings. The comment reads "…The examples below can be used to load some solr-contribs…", but the example code is not commented out. An example for using directory notation and one for regex notation are given for each extraction, clustering, langid and velocity. This makes up for eight Warnings per file or twentyfour in total. The remaining three Warnings come from the second issue, which is more serious I guess despite the lower count of warnings. I cant see any disadvantage when commenting out these eight examples. Second, around line 1260 starts another example for a RequestHandler registering with name="/spell". The comment starts with: "A request handler utilizing the spellcheck component." The comment also has an uppercase block stating "there is really good chance the setup below is not what you want for your production system". However, the example is not commented out. Actually, I would not even have noticed this if there were not still another example of similar kind about 200 lines below around line 1430 and with the same name="/spell". Its comment starts with "A request handler for demonstrating the spellcheck component." The comment contains the same advice in uppercase letters as before and the example is not commented out either. The Warning in catalina.out only comes from the fact that the name is used twice and the second handler cant be registered. I would never had the idea to tinker arount with the solr config when deploying DSpace. There is so much to configure, I dont go through every config setting to check whether it is fine for me. I expect the defaults to be safe for production use. As such, besides the warning I guess, these examples should be commented out. Or is this advice not valid any longer? In this case, the uppercase advice should be removed. In any case, it should be mentioned that not both RequestHandler examples can be activated at the same time, because people will probably spent time to find out, why the latter one does not work.
|
|
|
|