[Koha-bugs] [Bug 28736] Better error message when ES fails to understand the syntax of the search query

[bugzilla-daemon at bugs.koha-community.org]

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

--- Comment #7 from Andrew Nugged <nugged at gmail.com> ---
This "sub process_error" code was added here:
    e0f6c4dc Bug 12478: improve error reporting a bit
And it expected to get 'ParseException' inside of $@.

I didn't found any traces and explanations when we have text with
"ParseException" from ES, is it older ES versions that had such word?
(Search::Elasticsearch seems just propagates clean ES answer though)

Nowadays we have "parse_exception" in "$@" contents, in dumped JSON answer from
ES it contains answer body with "'type' => 'parse_exception'" value.

I don't think the "ParseException" presence will make future updates more
complicated but let's have this history-of-thoughts noted in the commit
message,


Part2: QA-follow-up: in my experience, I had a lot of users thinking that
"nothing was found", when ES error happened. I changed the phrase to be wordier
but to explain that there MIGHT be results, but the user needs to review his
request.

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