Multiple fq params are ANDed. So if you have fq=clause1 AND clause2, you should implement that as fq=clause1&fq=clause2. However, if you want fq=clause1 OR clause2, you have no choice but to keep it as a single filter query.
Upayavira On Mon, May 13, 2013, at 06:55 PM, Furkan KAMACI wrote: > Jason can you explain what you mean at here: "Where OR operators apply, > this does not matter. But your Solr cache will be much more savvy with > the > first construct." > > 2013/5/13 Lance Norskog <goks...@gmail.com> > > > If this is for the US, remove the age range feature before you get sued. > > > > > > On 05/09/2013 08:41 PM, Kamal Palei wrote: > > > >> Dear SOLR experts > >> I might be asking a very silly question. As I am new to SOLR kindly guide > >> me. > >> > >> > >> I have a job site. Using SOLR to search resumes. When a HR user enters > >> some > >> keywords say JAVA, MySQL etc, I search resume documents using SOLR, > >> retrieve 100 records and show to user. > >> > >> The problem I face is say, I retrieved 100 records, then we do filtering > >> for experience range, age range, salary range (using mysql query). > >> Sometimes it so happens that the 100 records I fetch , I do not get a > >> single record to show to user. When user clicks next link there might be > >> few records, it looks odd really. > >> > >> > >> I hope there must be some mechanism, by which I can associate salary, > >> experience, age etc with resume document during indexing. And when > >> I search for resumes I can give all filters accordingly and can retrieve > >> 100 records and strait way I can show 100 records to user without doing > >> any > >> mysql query. Please let me know if this is feasible. If so, kindly give me > >> some pointer how do I do it. > >> > >> Best Regards > >> Kamal > >> > >> > >
