Right, that patch is really about fixing the distribution solrconfig file...
What you need to do is (and I'm assuming you're running SolrCloud) is change the solrconfig.xml file, push it up to ZK with the client tools and restart all the nodes in your collection, or reload all the cores. I don't remember if the collections API that does this for you is in 4.0 or not.... If you're not running SolrCloud, you still need to up date all your configs _and_ restart (or reload) the cores. Best, Erick On Sun, Mar 2, 2014 at 9:03 PM, eShard <zim...@yahoo.com> wrote: > Hi, > I'm using Solr 4.0 Final (yes, I know I need to upgrade) > > I'm getting this error: > SEVERE: org.apache.solr.common.SolrException: no field name specified in > query and no default specified via 'df' param > > And I applied this fix: https://issues.apache.org/jira/browse/SOLR-3646 > And unfortunately, the error persists. > I'm using a multi shard environment and the error is only happening on one > of the shards. > I've already updated about half of the other shards with the missing default > text in /browse but the error persists on that one shard. > Can anyone tell me how to make the error go away? > > Thanks, > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SEVERE-org-apache-solr-common-SolrException-no-field-name-specified-in-query-and-no-default-specifiem-tp4120789.html > Sent from the Solr - User mailing list archive at Nabble.com.
