Thanks for the reply. I was in a hurry and made the URL up to illustrate my point. The real query string is more like what you suggest. In any case I'm certain that the actual query being used is valid (Solr would complain if it weren't) and that the ampersand is somehow affecting results. Is there any way I can get Solr to dump some information about how it stores indexes, keys, etc. for a certain record? I'm wondering if the ampersand was handled in a weird way by my application when the records were added to the index. (Although I doubt this since it shows up properly in the facets.) Thanks again for your help.
Jonathan hossman wrote: > > > : However, the following query produces no hits, even though I know from > the > : facets info that there are over 4000 matches in the index: > : > : > fl=*,score&start=0&q=division_t:"Accounting"&company_facet:"Deloitte+%26+Touche"&qt=standard&wt=ruby&rows=30 > > That's not a "legal" URL ... note the "...&company_facet...". You've > specified a URL param named: 'company_facet:"Deloitte+%26+Touche"' which > has no value. > > I think you ment to use... > > fl=*,score&start=0&q=division_t:"Accounting"&fq=company_facet:"Deloitte+%26+Touche"&qt=standard&wt=ruby&rows=30 > > : I was under the impression that Solr.StrField just indexes the literal > : string, so I'm confused why this won't work. What's the proper way to > feed > > the record: that is in fact exactly what StrField does. > > > -Hoss > > > -- View this message in context: http://www.nabble.com/How-does-solr.StrField-handle-punctuation--tp17759824p17956690.html Sent from the Solr - User mailing list archive at Nabble.com.
