Re[3]: Multiple fq fields in URL

: 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

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

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

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 ..