[Koha-bugs] [Bug 30836] Elasticsearch mappings.yaml is out of sync with upgraded databases

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

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

--- Comment #5 from Ere Maijala <ere.maijala at helsinki.fi> ---
I'm not sure if I can come up with a good solution. Automatically updating
current mappings can create problems when the defaults have been customized.

What we might be able to do is to check, field by field, if the mappings have
been customized, and apply any changes only on top of old defaults. I'm not
sure if that's feasible in real life, but worth a thought. At least it should
be possible to check that any mappings required by Koha are available
regardless of their configuration, and add any that are missing completely.
Perhaps a warning about updated mappings during upgrade would be useful as
well.

I think that in many cases requiring resetting to defaults would be too
destructive. Having to redo all customizations could be pretty a lot of work
unless you manage them in a customized mappings.yaml or something. It would be
useful to have a tool that would show the differences between current and
default mappings. This would make it easier to determine any manual changes
needed or useful.

All in all, I'm not sure I like having the database part of the configuration.
Sure, the UI makes it easier to start changing the mappings, but if you need to
do more, it's cumbersome. Also changing the settings can have consequences that
you need to be aware of, and sometimes I feel it should not be that easy to
change them.

Regardless of how the mappings update is managed, any changes will need to
trigger a prominent notification that reindexing is required.

Sorry for this being a collection of random thoughts...

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