I had actually totally blown my previous configuration and didn't know it (luckily it didn't reach production this way). I'm glad I ran into this problem. I had defaulted the queries to one of the most useful fields and never realized I wasn't searching the others. Thanks very much for all your help on this, it certainly helped me get my configuration straight and the upgrade to 4 is now complete.
All the best, David -----Original Message----- From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Wednesday, March 06, 2013 7:56 PM To: solr-user@lucene.apache.org; David Parks Subject: Re: After upgrade to solr4, search doesn't work I imagine that you had a "qf" parameter in your old query request handler, so add "qf" it to the new query request handler. "df" is used only if "qf" is missing. -- Jack Krupansky -----Original Message----- From: David Parks Sent: Wednesday, March 06, 2013 2:18 AM To: solr-user@lucene.apache.org ; David Parks Subject: Re: After upgrade to solr4, search doesn't work Ah, I think I see the issue, in the debug results it's only searching the id field, which is the unique ID, that must have gotten changed in the upgrade. In fact I think I might have had a misconfiguration in the 3.x version here. Can I set it to query multiple fields by default? I tried a comma separated list of my fields here but that was invalid. <result name="response" numFound="0" start="0"></result><lst name="debug"><str name="rawquerystring">dvd</str><str name="querystring">dvd</str><str name="parsedquery">id:dvd</str><str name="parsedquery_toString">id:dvd</str> ________________________________ From: David Parks <davidpark...@yahoo.com> To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> Sent: Wednesday, March 6, 2013 1:52 PM Subject: Re: After upgrade to solr4, search doesn't work Good though, thanks for the quick reply too. Seems that this is still set to my unique ID field: <requestHandler name="/select" class="solr.SearchHandler"> <!-- default values for query parameters can be specified, these will be overridden by parameters in the request --> <lst name="defaults"> <str name="echoParams">explicit</str> <int name="rows">10</int> <str name="df">id</str> </lst> I wonder if I have somehow lost the configuration that specifies that the other fields should be searched as well, though my schema hasn't changed and they're certainly indexed: <field name="_version_" type="long" indexed="true" stored="true" multiValued="false"/><!-- FRUGG FIELDS --><field name="id" type="string" indexed="true" stored="true" required="true" version="1.5" /><field name="item_name" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="item_brand" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="short_description" type="text_en_splitting" indexed="true" stored="true" multiValued="true" termVectors="true" version="1.5" /><field name="long_description" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="catalog_names" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="categories" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="keywords" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="attributes" type="text_en_splitting" indexed="true" stored="false" multiValued="true" termVectors="true" version="1.5" /><field name="facetime" type="long" indexed="true" stored="true" multiValued="false" version="1.5" /><!-- Used to group by the largest catalog name --><field name="unique_catalog_name" type="string" indexed="true" stored="false" multiValued="false" version="1.5" /> ________________________________ From: Jack Krupansky <j...@basetechnology.com> To: solr-user@lucene.apache.org Sent: Wednesday, March 6, 2013 1:34 PM Subject: Re: After upgrade to solr4, search doesn't work You may simply need to set the default value of the "df" parameter in the /select request handler in solrconfig.xml to be your default query field name if it is not "text". -- Jack Krupansky -----Original Message----- From: David Parks Sent: Wednesday, March 06, 2013 1:26 AM To: solr-user@lucene.apache.org Subject: After upgrade to solr4, search doesn't work I just upgraded from solr3 to solr4, and I wiped the previous work and reloaded 500,000 documents. I see in solr that I loaded the documents, and from the console, if I do a query "*:*" I see documents returned. I copied a single word from the text of the query results I got from "*:*" but any query I do with a term returns 0 results, even though it's clear from the "*:*" query that solr has that document. Any ideas on where to start looking here? David
