https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29893 Bug ID: 29893 Summary: ElasticSearch Config UI deletes mappings Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: domm@plix.at When using the Elasticsearch UI /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl to edit search mappings one can quite easily delete a lot of mappings by mistake. To reproduce: * go to /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl * click on the "Authorities" Tab * You should see ~ "67 entries" * enter "Heading-Main" into the search field, you now see ~8 entries ("filtered from 67 entries" * Click "save" Button * Go again to the "Autorities" Tab * You now see ~ "8 entries" * All the other entries have been deleted! What obviously happens is that all entries that where filtered due to the search are not submitted to the backend on save. The backend now interprets the missing entries as entries that shall be deleted. And happily deleted them! This totally breaks the search index (after the next index run, or when adding single items), as (eg in the auth-index) "authtype" is no longer indexed. I currently don't have a 21.11 or later version at hand, so maybe this has already been fixed? To fix this bug we would either have to un-hide the filtered entries before submitting the form; change the backend to not deleted missing entries (which means that the delete-action would have to be implemented a bit different); something else? I guess that the first fix is easier, and would also make sense with regard to how that form works. Greetings, domm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.