Bug 28899 - Don't always make = into : for elastic range searching
Summary: Don't always make = into : for elastic range searching
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-25 20:26 UTC by Andrew Fuerste-Henry
Modified: 2024-05-23 06:25 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2021-08-25 20:26:14 UTC
For range searches, Elastic supports searches for ranges with one end bound, like "pubdate greater than or equal to 2020." Except the phrasing for that would be "pubdate:>=2020." And Koha wants to let us use either a colon or an equals sign after our index name, so it always converts an equals sign in to a colon, which means our query turns into "pubdate:>:2020" and we get an error.
Comment 1 David Cook 2024-05-23 06:25:16 UTC
Is this still valid? 

I'm passing acqdate:>2000-05-01 to Koha::SearchEngine::Search->new->simple_search_compat() in a workaround for bug 30745 and it's not mangling it.