-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting by score in searchService.cfc not working #13
Comments
Could you dump this right after this line to see if the value stuck https://github.com/blueriver/MuraSolr/blob/master/lib/searchService.cfc#L409
|
|
I modified final query at ln 431. (alias score as scorey)
Thanks for that snippet - was looking in the wrong place. It was indeed returning the correct sort, just not displaying the correct score. However, for some reason my search pulls 3 other results ahead of a page with exact title, metadesc, and summary that matches my term. I can manipulate results with 'tags' but and sorting by tags first. I guess I just can't understand why solr can't see a pages with an exact term as most relevant. |
I think the issue is that query is treating the score column like an integer. I think the score value coming from solr needs to be multiplied by 1000 when added to the rs query variable. Just an educated guess. I see what you did by adding the join. I check that out. |
Hi - Think I've uncovered a bug - not sure if it's related to CF10/MSSQL or and oddity with QoQ in CF10, or something else (or even if it is indeed a bug):
Try this at ln 403: cfquery name="rsScore" dbtype="query"
select contentID,score ,context from rsDbSearch
where contentID=
/cfquery
< cfdump var="#rsScore#" >
and add this:
The rsScore dump dumps the correct score (0.3227 etc) , rs dumps 0.
Basically - it returns the '0' value set in the rs query at line 300 and NOT the correct score.SO... upshot is that it always returns '0' instead of the correct querysetcell at ln 408.
For my test search I used a quoted phrase - e.g. "My search term" .
Still trying to fix it from my end - if I come up with a solution before you do I'll share it here....
cheers
jon
The text was updated successfully, but these errors were encountered: