Moving from SOLR3.6 to SOLR4.0 - Last remaining warnings
Hi. I have recently made the move from SOLR3.6 to SOLR4.0 and so far everything seems super apart frmo the fact that I had a lot of warnings in my logging section on the solr admin panel. I have tried to work through as many as possible but I have a few that I am not able to correct. This is the hot list: === 11:56:41 WARNING IndexSchema uniqueKey is not stored - distributed search and MoreLikeThis will not work 11:56:41 WARNING SolrCore [collection1] Solr index directory '/opt/solr/example/solr/collection1/data/index' doesn't exist. Creating new index... 11:56:42 WARNING UpdateRequestHandler Using deprecated class: XmlUpdateRequestHandler -- replace with UpdateRequestHandler 11:56:42 WARNING UpdateRequestHandler Using deprecated class: BinaryUpdateRequestHandler -- replace with UpdateRequestHandler === Would anyone please mind explaining to me where I am going wrong to get these errors? It looks like content in my configs is causing them but for the most part my configurations are pretty standard. Any help or advice would be much appreciated. James -- View this message in context: http://lucene.472066.n3.nabble.com/Moving-from-SOLR3-6-to-SOLR4-0-Last-remaining-warnings-tp4054459.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Moving from SOLR3.6 to SOLR4.0 - Last remaining warnings
Here's my guess. On 4/8/13 4:04 AM, Spadez wrote: 11:56:41 WARNING IndexSchema uniqueKey is not stored - distributed search and MoreLikeThis will not work I think the warning is saying the field you specify in uniqueKey does not specify stored=true. Check your schema.xml. 11:56:41 WARNING SolrCore [collection1] Solr index directory '/opt/solr/example/solr/collection1/data/index' doesn't exist. Creating new index... This is normal. 11:56:42 WARNING UpdateRequestHandler Using deprecated class: XmlUpdateRequestHandler -- replace with UpdateRequestHandler 11:56:42 WARNING UpdateRequestHandler Using deprecated class: BinaryUpdateRequestHandler -- replace with UpdateRequestHandler UpdateRequestHandler now takes care of XML, JSON, CSV and binary document formats by itself. No specialized subclasses like XmlUpdateRequestHandler should be used. All these deprecated subclasses add is output of this deprecation warning. But you can ignore these warnings for this version of Solr. -- Kuro Kurosaka
Re: Moving from SOLR3.6 to SOLR4.0 - Last remaining warnings
replace with UpdateRequestHandler Just compare your solrconfig to the new one and consider updating yours and using the newer Solr update API that automatically uses the content type to internally dispatch to the proper update handler. But, it's just a warning, for now. -- Jack Krupansky -Original Message- From: Kuro Kurosaka Sent: Monday, April 08, 2013 12:57 PM To: solr-user@lucene.apache.org Subject: Re: Moving from SOLR3.6 to SOLR4.0 - Last remaining warnings Here's my guess. On 4/8/13 4:04 AM, Spadez wrote: 11:56:41 WARNING IndexSchema uniqueKey is not stored - distributed search and MoreLikeThis will not work I think the warning is saying the field you specify in uniqueKey does not specify stored=true. Check your schema.xml. 11:56:41 WARNING SolrCore [collection1] Solr index directory '/opt/solr/example/solr/collection1/data/index' doesn't exist. Creating new index... This is normal. 11:56:42 WARNING UpdateRequestHandler Using deprecated class: XmlUpdateRequestHandler -- replace with UpdateRequestHandler 11:56:42 WARNING UpdateRequestHandler Using deprecated class: BinaryUpdateRequestHandler -- replace with UpdateRequestHandler UpdateRequestHandler now takes care of XML, JSON, CSV and binary document formats by itself. No specialized subclasses like XmlUpdateRequestHandler should be used. All these deprecated subclasses add is output of this deprecation warning. But you can ignore these warnings for this version of Solr. -- Kuro Kurosaka
Re: Moving from SOLR3.6 to SOLR4.0 - Last remaining warnings
On Apr 8, 2013, at 19:09 , Jack Krupansky j...@basetechnology.com wrote: replace with UpdateRequestHandler Just compare your solrconfig to the new one and consider updating yours and using the newer Solr update API that automatically uses the content type to internally dispatch to the proper update handler. But, it's just a warning, for now. It would probably be a good idea to split solrconfig, so that settings specific to a SOLR version would be separate from settings that mainly (only?) depend on the schema... I was quite surprised when I had to re-do my modifications tol solrconfig.xml when moving from 4.0 to 4.1.
