Bug 22829 - Elasticsearch - some blank subfields cause parsing errors during indexing
Summary: Elasticsearch - some blank subfields cause parsing errors during indexing
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-02 11:47 UTC by Nick Clemens
Modified: 2021-10-08 17:48 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens 2019-05-02 11:47:00 UTC
Some fields in the record cause errors during indexing if they exist but are blank

To recreate:
1 - Use the koha sample data or edit a record using the advanced cataloging editor and blank 100$a (probably also shouldn't be allowed)
2 - Save record
3 - Reindex ES
4 - Note you cannot search for the record

bug 22828 will show you the error from ES
Comment 1 Caroline Cyr La Rose 2021-05-12 20:56:47 UTC
I've run into this problem also. I think the records had been migrated from another system and a lot of 245$b were simply blank. ES did not like this.

This is the (very cryptic) error message
Use of uninitialized value $_ in pattern match