Re: Trouble boosting a field -solved-

2017-01-18 Thread Tom Chiverton
I 'solved' this by removing some of the 'AND' from my full query. AND should be optional but have no effect if there, right ? But for me it was forcing the score to 0. Which might be the same as saying nothing matched ? Tom On 13/01/17 15:10, Tom Chiverton wrote:

Re: Trouble boosting a field

2017-01-16 Thread Tom Chiverton
On 13 Jan 2017, at 16:35, Tom Chiverton wrote: Well, I've tried much larger values than 8, and it still doesn't seem to do the job ? For now, assume my users are searching for exact sub strings of a real title. Tom On 13/01/17 16:22, Walter Underwood wrote: I use a boost of 8 fo

Re: Trouble boosting a field

2017-01-13 Thread Tom Chiverton
"wt": "json", but that was not better. if I remove content from pf/qf then documents seem to rank correctly. Example query and results (content omitted) : http://pastebin.com/5EhrRJP8 <http://pastebin.com/5EhrRJP8> with managed-schema http://pastebin.com/mdraWQWE <

Trouble boosting a field

2017-01-13 Thread Tom Chiverton
", "defType": "dismax", "indent": "true", "qf": "title^2000 content", "pf": "pf=title^4000 content^2", "sort": "score desc", "wt": "json", but that was not better. if I