Re[3]: Multiple fq fields in URL

2007-05-14 Thread Chris Hostetter
: q=samsung+camera : : And if samsung is mandatory, the query will be like this: (or not:) : : q=+samsung+camera : : And the first + will be interpreted as mandatory flag? No. bottom line, forget all about URLs and URL escape. step #1: understand the Lucene query syntax... http://lucene

Re: Re[3]: Multiple fq fields in URL

2007-05-13 Thread Erik Hatcher
Jack, On May 13, 2007, at 6:45 PM, Jack L wrote: 1. I didn't understand the part above in your reply. If I search for samsung camera, the query should be like this in the select URL: q=samsung+camera And if samsung is mandatory, the query will be like this: (or not:) q=+samsung+camera

Re[3]: Multiple fq fields in URL

2007-05-13 Thread Jack L
Hello Chris, When I read your email again, I find that I didn't understand it very well, because although fq works for me now, when I need to construct the q variable, I run into the same set of questions and am still not clear :) > : BTW, space is sometimes encoded as %20, sometimes as "+". > :

Re[3]: Multiple fq fields in URL

2007-05-07 Thread Jack L
Hello Chris, Thanks a lot for the explanation. Get well soon! -- Best regards, Jack Saturday, May 5, 2007, 9:02:36 PM, you wrote: > start by ignoring the URL escaping, treat the concept of a filter query > exactly as you would any other lucene query string for the standard > request handler ..

Re[2]: Multiple fq fields in URL

2007-05-05 Thread Chris Hostetter
: Thanks for the reply. And sorry for sounding impatient - : I've been working in the weekend and I wasn't sure if I expressed : my question well, hence why the second email :) yeah .. my apologies as well, i realize now i didn't answer your question very well at all ... i've been sick and it's

Re[2]: Multiple fq fields in URL

2007-05-05 Thread Jack L
Hello Chris, Thanks for the reply. And sorry for sounding impatient - I've been working in the weekend and I wasn't sure if I expressed my question well, hence why the second email :) I understand I can url-encode the space. My question, which I failed to mention in my first email, is that, what

Re: Multiple fq fields in URL

2007-05-05 Thread Chris Hostetter
first off, please have a little patience when sending mai lto the mailing list ... 17 hours between "reposting" isn't relaly a lot ... especially on a weekend, when many people are out of hte country for a confrence, and i'm sick :) On to your question... : fq=+popularity:[10 TO *] +section:0 :

Re: Multiple fq fields in URL

2007-05-05 Thread Jack L
Could anyone please explain a bit about the line below? No spaces is allowed in a URL so I suppose this needs to be quoted, but, what if there is space in the fq value field, which will create ambiguity between fq field boundary and term boundary? fq=+popularity:[10 TO *] +section:0 > I'm not su

Multiple fq fields in URL

2007-05-05 Thread Jack L
Hello , I'm not sure if I understand how to specify multiple fq in CommonQueryParameters, which is described in this page http://wiki.apache.org/solr/CommonQueryParameters It says: --- cut - fq=+popularity:[10 TO *] +section:0 is equivalent to fq=popularity:[10 TO *]&fq=section:0