It was not matching the results for that particular field
below is the debug data
(+DisjunctionMaxQuerynameSearchNoSyn:7 nameSearchNoSyn:armour)~2)^9.0 |
((brandSearch:7 brandSearch:armour)~2) | ((nameSearch:7
nameSearch:armour)~2)^4.0 | (keywords:7 armour)^11.0 | ((descSearchNoSyn:7
descSearc
Interesting.
it seems almost correct to me.
Have you explored the content of the field ( for example using the schema
browser) ?
When you say " don't match" it means you don't get results at all or just
the boost is not applied ?
I would recommend to simply the request handler, maybe just introduci
Sorry Rick,
I didn't get it.
How will you give boost on other field when querying on some other field.
Or if you query on copy keyword tokenized field then it only matched when
entire query is matched.
On 20-Jun-2017 1:52 AM, "Rick Leir" wrote:
Aman,
Use a copyfield so you can have a second fie
Aman,
Use a copyfield so you can have a second field that uses a different analysis
chain. In the new field you just created for the copyfield, use the lowercase
type, or create a type using KeywordTokenizer in the analysis chain. Then match
on the original field, and boost based on the new fiel
Yes alessandro,
I know that their us some downsight of using sow =false but if don't use
it then neither shingle nor bhram will work ,and these are required in my
case/setup
On 19-Jun-2017 8:18 PM, "alessandro.benedetti" wrote:
Isn't this a case where you don't want the query parser to split by
Yes Susheel ,
I know that more token matched gives more weight but in my case if entire
match I want around x times boost but in case of partial match I want to
give nominal boost or normal boost,
Now in case of keyword token ziet or phrase query they work if and only if
the user query is exactly m
Isn't this a case where you don't want the query parser to split by space
before the analyser ?
Take a look to the "sow" param for the edismax query parser.
In your case you should be ok but Be aware that is not a silver bullet for
everything and that other problems could arise in similar scenarios
In general, the documents which has more or all terms matched against query
terms will be boosted higher per lucene tf/idf scoring.
So for document having ABC DEF queries like ABC DEF XYZ or XYZ ABC DEF
will find a match(assuming q.op=AND) and will be boosted higher compare to
documents with ABC
