Closed JasonBarnabe closed 7 years ago
Thanks Jason, just pushed a fix for this in 60df63108b6a67b9740f8b277886526d8aa79738, which you can use from the develop
branch if you wish.
It's worth noting the underlying warning is caused by invalid search options in the search call - so if you don't want to use the develop branch, it's worth double-checking the options you're passing through - fix that up and you'll avoid seeing the lengthy error in your logs. I'll look at pushing a new patch release in the coming week or so.
FWIW, 3.4.2 is now released with a fix for this.
Also, I found out that some valid options weren't covered in my validation, so it's quite possible you weren't using anything invalid to begin with!
Thanks, this worked. Turns out the offending option was match_mode
, which I found is no longer used.
Ruby 2.4.2 Sphinx 2.2.11-id64-release Rails 5.1.4 Full code: https://github.com/JasonBarnabe/greasyfork/tree/0f3fac2bb13e52552c43d182c55c948ce39bfa97
After upgrade of thinking-sphinx from 3.3.0 to 3.4.1, upon performing any search, I receive this in the log (the search seemingly works fine):