Re: filter query parameter not working as expected

2011-07-25 Thread Erick Erickson
Well, WAY_ANALYZED:de l hotel de ville parses as WAY_ANALYZED:de default:l default:hotel default:de default:ville You probably want something like WAY_ANALYZED:(de l hotel de ville), perhaps with AND between them. Try adding debugQuery=on to your queries and you can sometimes see this kind of

Re: filter query parameter not working as expected

2011-07-25 Thread elisabeth benoit
thanks using parenthesis select?q=VINCI Parkfq=WAY_ANALYZED:(rue de l hotel de ville) AND (TOWN_ANALYZED:paris OR DEPARTEMENT_ANALYZED:paris)rows=200fl=NAME,TOWN,WAY,scoredebugQuery=on works but I would rather not use parenthesis or AND between those words this brings another question:

Re: filter query parameter not working as expected

2011-07-25 Thread Erick Erickson
Not that I know of, although it does give you the parsed fq results, which you could then use as query parameters (i.e. the 'q' parameter) for debugging... You have to use parens or fully qualify each term (e.g. WAY_ANALYZED:rue WAY_ANALYZED:de), that's just how the query parsing works...

filter query parameter not working as expected

2011-07-21 Thread elisabeth benoit
Hello, There is something I don't quite get with fq parameter. I have this query select?q=VINCI Parkfq=WAY_ANALYZED:de l hotel de ville AND (TOWN_ANALYZED:paris OR DEPARTEMENT_ANALYZED:paris)rows=200fl=*,score and two answers. One having WAY_ANALYZED = 48 r de l'hôtel de ville, which is ok