Fix the case when using order_by_function with Solr strdist #572
Conversation
* Added testing with valid and invalid measure options
|
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
|
Very useful ! |
|
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
|
Why not just accept any arguments to strdist and let solr explode if the param is invalid instead of needing to keep a list of valid measures up to date with solr? |
| else | ||
| raise( | ||
| UnrecognizedRestrictionError, | ||
| "Use only valid measure options with strdist (#{valid_measures.to_s})" |
There was a problem hiding this comment.
Object#to_s in interpolation.
When using the Solr strdist FunctionQuery with the new
order_by_functionit is required to include a distance measure to use, but sunspot consider each param as it were fields, this pull request fixes that situation.