[Koha-bugs] [Bug 12430] Using QueryAutoTruncate breaks relevance ranking

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Feb 4 19:51:13 CET 2020


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430

--- Comment #23 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Martin Renvoize from comment #22)
> De-escalating this one.. it's been around for 6 years and hasn't really
> recieved the attention a critical should.. I personally feel at the time it
> was critical and it's still a nice to fix.. but as we're moving toward
> elastic search and possible deprecating QueryParser entirely I'm not sure
> how to progress this bug.

I'd argue it's still a very bad bug and Elastic not ready yet for wide use yet
(thinking of libraries without IT experts and support especially). As it breaks
things when NOT using QueryParser, there is no link to that. It hurts a lot of
our libraries and is very hard to figure out - I think we shoudl really fix it.
The sole reason it was not fixed yet is probably people are scared of
Search.pm.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list